blocks|key|3779089|text|FiveRuns有一个名为DataFabric的gem，它执行应用程序级别的分片和主/从复制。这可能值得一查。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3779090|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/bpot/data_fabric^0|D|A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

FiveRuns have a gem named <a href="https://github.com/bpot/data_fabric" rel="nofollow noreferrer">DataFabric</a> that does application-level sharding and master/slave replication. It might be worth checking out.

blocks|key|724638|text|我假设对于分片，我们谈论的是水平分区而不是垂直分区(here+are+the+differences+on+Wikipedia。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|724639|首先，在考虑水平分区之前，尽可能地扩展垂直分区。在Rails中，让不同的模型指向不同的机器是很容易的，对于大多数Rails站点来说，这已经足够了。|style|BOLD|724640|对于水平分区，在理想情况下，这将在Rails中的应用程序层中处理。但是，虽然这并不难，但在Rails中并不是微不足道的，当您需要它的时候，您的应用程序通常已经超出了可行的范围，因为您的ActiveRecord调用随处可见。没有人，开发人员或管理人员，喜欢在你需要它之前工作，因为每个人都更愿意在用户现在使用的功能上工作，而不是在你的流量爆炸后几年内不会发挥作用的分区。|724641|ActiveRecord+layer...据我所知并不容易。将需要大量的猴子补丁到Rails内部。|724642|在Spock，我们最终使用定制的MySQL+proxy来处理这个问题，并将其作为Spock+Proxy在SourceForge上开源。ActiveRecord认为它是在与一台MySQL数据库机器对话，而实际上它是在与代理对话，然后代理与一个或多个MySQL数据库对话，合并/排序结果，并将结果返回给ActiveRecord。只需要对Rails代码进行少量更改。请查看Spock代理SourceForge页面，了解更多详细信息以及我们选择此路线的原因。|724643|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Partition_(database%2529)|1|http://www.spock.com/about|2|http://spockproxy.sourceforge.net/^0|Q|11|0|0|D|A|0|O|5|0|0|I|0|D|E|1|5|1|14|B|2|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|6|7|13|8|@$A|14|B|15|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|16|8|@$A|17|B|18|F|G]]|9|@]|C|$]]|$1|J|3|K|5|6|7|19|8|@$A|1A|B|1B|F|G]]|9|@]|C|$]]|$1|L|3|M|5|6|7|1C|8|@$A|1D|B|1E|F|G]]|9|@$A|1F|B|1G|1|1H]|$A|1I|B|1J|1|1K]]|C|$]]|$1|N|3|-4|5|6|7|1L|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]|V|$5|Q|R|S|C|$T|W]]|X|$5|Q|R|S|C|$T|Y]]]]

I assume with shards we're talking about horizontal partitioning and not vertical partitioning (<a href="http://en.wikipedia.org/wiki/Partition_(database)" rel="noreferrer">here are the differences on Wikipedia</a>).

First off, stretch vertical partitioning as far as you can take it before you consider horizontal partitioning. It's easy in Rails to have different models point to different machines and for most Rails sites, this will bring you far enough.

For horizontal partitioning, in an ideal world, this would be handled at the application layer in Rails. But while it's not hard, it's not trivial in Rails, and by the time you need it, usually your application has grown beyond the point where this is feasible since you have ActiveRecord calls sprinkled all over the place. And no one, developers or management, likes working on it before you need it since everyone would rather work on features users will use now rather than on partitioning which may not come into play for years after your traffic has exploded.

ActiveRecord layer... not easy from what I can see. Would require lots of monkey patching into Rails internals.

At <a href="http://www.spock.com/about" rel="noreferrer">Spock</a> we ended up handling this using a custom MySQL proxy and open sourced it on SourceForge as <a href="http://spockproxy.sourceforge.net/" rel="noreferrer">Spock Proxy</a>. ActiveRecord thinks it's talking to one MySQL database machine when reality it's talking to the proxy, which then talks to one or more MySQL databases, merges/sorts the results, and returns them to ActiveRecord. Requires only a few changes to your Rails code. Take a look at the Spock Proxy SourceForge page for more details and for our reasons for going this route.

blocks|key|3779052|text|对于像我这样没有听说过分片的人：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3779053|http://highscalability.com/unorthodox-approach-database-design-coming-shard|offset|length|3779054|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|23|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

For those of you like me who hadn't heard of sharding:

<a href="http://highscalability.com/unorthodox-approach-database-design-coming-shard" rel="noreferrer">http://highscalability.com/unorthodox-approach-database-design-coming-shard</a>

blocks|key|3779188|text|将Rails连接到多个数据库并不是什么大问题-您只需为覆盖connection属性的每个分片创建一个ActiveRecord子类即可。如果您需要进行跨分片调用，这会使它变得非常简单。然后，当您需要在分片之间进行调用时，您只需编写一些代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3779189|我不喜欢Hank拆分rails实例的想法，因为除非你有一个很大的共享库，否则在实例之间调用代码似乎很有挑战性。|3779190|另外，在开始分片之前，你应该考虑做一些像Masochism这样的事情。|offset|length|3779191|entityMap|0|LINK|mutability|MUTABLE|url|http://github.com/technoweenie/masochism/tree/master^0|0|0|K|9|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

Connecting Rails to multiple databases is not a big deal- you simply have an ActiveRecord subclass for each shard that overrides the connection property. That makes it pretty simple if you need to make cross-shard calls. You then just have to write a little code when you need to make calls between the shards. 

I don't like Hank's idea of splitting the rails instances, because it seems challenging to call the code between the instances unless you have a big shared library.

Also you should look at doing something like <a href="http://github.com/technoweenie/masochism/tree/master" rel="nofollow noreferrer">Masochism</a> before you start sharding.

blocks|key|3779372|text|为了让rails与复制环境协同工作，我建议使用my_replication插件，它可以帮助在运行时将数据库连接切换到其中一个从服务器|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3779373|https://github.com/minhnghivn/my_replication|offset|length|3779374|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|18|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

For rails to work with replicated environment, I would suggest using my_replication plugin which helps switch database connection to one of the slaves at run-time

<a href="https://github.com/minhnghivn/my_replication" rel="nofollow">https://github.com/minhnghivn/my_replication</a>

blocks|key|2934175|text|rails+6.1提供了为每个数据库切换连接的能力，因此我们可以进行水平分区。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2934176|2934177|分片在三层配置中声明如下：|unordered-list-item|2934178|2934179|production:
++primary:
++++database:+my_primary_database
++++adapter:+mysql2
++primary_replica:
++++database:+my_primary_database
++++adapter:+mysql2
++++replica:+true
++primary_shard_one:
++++database:+my_primary_shard_one
++++adapter:+mysql2
++primary_shard_one_replica:
++++database:+my_primary_shard_one
++++adapter:+mysql2
++++replica:+true|code-block|syntax|javascript|2934180|然后，|2934181|模型通过分片密钥|2934182|与connects_to应用编程接口连接|2934183|class+ApplicationRecord+<+ActiveRecord::Base
++self.abstract_class+=+true

++connects_to+shards:+{
++++default:+{+writing:+:primary,+reading:+:primary_replica+},
++++shard_one:+{+writing:+:primary_shard_one,+reading:+:primary_shard_one_replica+}
++}
end|2934184|2934185|模型可以通过connected_to应用编程接口手动交换连接。如果使用分片，则必须同时传递角色和分片：|2934186|2934187|ActiveRecord::Base.connected_to(role:+:writing,+shard:+:shard_one)+do
++@id+=+Person.create!+#+Creates+a+record+in+shard+one
end

ActiveRecord::Base.connected_to(role:+:writing,+shard:+:shard_one)+do
++Person.find(@id)+#+Can't+find+record,+doesn't+exist+because+it+was+created
+++++++++++++++++++#+in+the+default+shard
end|2934188|参考资料：|2934189|2934190|https://edgeguides.rubyonrails.org/active_record_multiple_databases.html#horizontal-sharding|offset|length|2934191|https://dev.to/ritikesh/multitenant-architecture-on-rails-6-1-27c7|2934192|2934193|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|2K|0|0|0|1U|1|0|0^^$0|@$1|2|3|4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|1L|8|@]|9|@]|A|$J|K]]|$1|L|3|M|5|6|7|1M|8|@]|9|@]|A|$]]|$1|N|3|O|5|E|7|1N|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1O|8|@]|9|@]|A|$]]|$1|R|3|S|5|I|7|1P|8|@]|9|@]|A|$J|K]]|$1|T|3|M|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|U|3|V|5|E|7|1R|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|X|3|Y|5|I|7|1T|8|@]|9|@]|A|$J|K]]|$1|Z|3|10|5|6|7|1U|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]|$1|12|3|13|5|E|7|1W|8|@]|9|@$14|1X|15|1Y|1|1Z]]|A|$]]|$1|16|3|17|5|E|7|20|8|@]|9|@$14|21|15|22|1|23]]|A|$]]|$1|18|3|-4|5|6|7|24|8|@]|9|@]|A|$]]|$1|19|3|-4|5|6|7|25|8|@]|9|@]|A|$]]]|1A|$1B|$5|1C|1D|1E|A|$1F|13]]|1G|$5|1C|1D|1E|A|$1F|17]]]]

rails 6.1 provides ability to switch connection per database thus we can do the horizontal partitioning.
<ul>
<li>Shards are declared in the three-tier config like this:</li>
</ul>
<pre class="lang-yaml prettyprint-override"><code>production:
 primary:
 database: my_primary_database
 adapter: mysql2
 primary_replica:
 database: my_primary_database
 adapter: mysql2
 replica: true
 primary_shard_one:
 database: my_primary_shard_one
 adapter: mysql2
 primary_shard_one_replica:
 database: my_primary_shard_one
 adapter: mysql2
 replica: true
</code></pre>
<ul>
<li>Models are then connected with the connects_to API via the shards key</li>
</ul>
<pre class="lang-rb prettyprint-override"><code>class ApplicationRecord &lt; ActiveRecord::Base
 self.abstract_class = true

 connects_to shards: {
 default: { writing: :primary, reading: :primary_replica },
 shard_one: { writing: :primary_shard_one, reading: :primary_shard_one_replica }
 }
end
</code></pre>
<ul>
<li>Then models can swap connections manually via the connected_to API. If using sharding, both a role and a shard must be passed:</li>
</ul>
<pre class="lang-rb prettyprint-override"><code>ActiveRecord::Base.connected_to(role: :writing, shard: :shard_one) do
 @id = Person.create! # Creates a record in shard one
end

ActiveRecord::Base.connected_to(role: :writing, shard: :shard_one) do
 Person.find(@id) # Can't find record, doesn't exist because it was created
 # in the default shard
end
</code></pre>
<h3>reference:</h3>
<ul>
<li><a href="https://edgeguides.rubyonrails.org/active_record_multiple_databases.html#horizontal-sharding" rel="nofollow noreferrer">https://edgeguides.rubyonrails.org/active_record_multiple_databases.html#horizontal-sharding</a></li>
<li><a href="https://dev.to/ritikesh/multitenant-architecture-on-rails-6-1-27c7" rel="nofollow noreferrer">https://dev.to/ritikesh/multitenant-architecture-on-rails-6-1-27c7</a></li>
</ul>

blocks|key|724583|text|在我看来，最简单的方法是在rails实例和DB分片之间保持1:1的关系。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|724584|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

To my mind, the simplest way is maintain a 1:1 between rails instances and DB shards.

blocks|key|2934392|text|代理层更好，它可以支持所有的编程语言。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2934393|例如:+Apache+ShardingSphere‘proxy。|2934394|Apache有两种不同的产品，一种是只针对Java语言的应用层的ShardingSphere，另一种是针对所有编程语言的代理层的代理。|2934395|仅供参考：https://shardingsphere.apache.org/document/current/en/user-manual/shardingsphere-proxy/|offset|length|2934396|entityMap|0|LINK|mutability|MUTABLE|url|https://shardingsphere.apache.org/document/current/en/user-manual/shardingsphere-proxy/^0|0|0|0|5|2F|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@$H|V|I|W|1|X]]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

Proxy layer is better, it can support all program languages.
For example: Apache ShardingSphere' proxy.
There are 2 different products of Apache ShardingSphere, ShardingSphere-JDBC for application layer which for Java language only and ShardingSphere-Proxy for proxy layer which for all program languages.
FYI: <a href="https://shardingsphere.apache.org/document/current/en/user-manual/shardingsphere-proxy/" rel="nofollow noreferrer">https://shardingsphere.apache.org/document/current/en/user-manual/shardingsphere-proxy/</a>

blocks|key|3779646|text|取决于rails版本。更新的rails版本提供了对分片的支持，正如@Oshan所说的那样。但是如果你不能更新到新的版本，你可以使用octopus+gem。Gem链接https://github.com/thiagopradi/octopus|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3779647|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/thiagopradi/octopus^0|2A|12|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Depends upon rails version. Newer rails version provide support for sharding as said by @Oshan. But if you can't update to a newer version you can use the octopus gem.
Gem Link
<a href="https://github.com/thiagopradi/octopus" rel="nofollow noreferrer">https://github.com/thiagopradi/octopus</a>

What's the best way to deal with a sharded database in Rails? Should the sharding be handled at the application layer, the active record layer, the database driver layer, a proxy layer, or something else altogether? What are the pros and cons of each?

Database sharding and Rails

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

在Rails中处理分片数据库的最好方法是什么？是否应该在应用层、活动记录层、数据库驱动器层、代理层或其他层处理分片？每种方法的优缺点是什么？

问数据库分片和Rails
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问数据库分片和RailsEN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问数据库分片和Rails
EN