Sharding is a particularly cost-effective decision for organizations tied to a relational infrastructure that cannot continue to upgrade hardware to meet the need for massively scalable data storage.
切分对于绑定于关系基础架构、无法继续升级硬件以满足大量可伸缩数据存储要求的组织来说是一个非常成本高效的决策。
Sharding also conceivably improves reliability, because even if one shard unexpectedly fails, others are still able to serve data.
切分还可以改善可靠性，因为即便一个切分意外失效，其他切分仍然可以服务数据。
In the Microsoft sharding pattern a "sharding key" is used to map data to specific shards which is the primary key in one of the data entities.
在微软的分片模式中，“分片键”用于将数据映射到特定的分片上，后者就是一个数据实体的主键。
Sharding collection is preferable because in many cases some data collections tend to be much larger than others, so it would be unprofitable to distribute the entire database.
Sharding是非常合适的解决方案，因为在多数情况下，数据收集会比其它操作要频繁的多，没必要每次都去分配整个数据库。
The benefit of sharding (like partitioning) is that it compacts big data: individual tables are smaller in each shard, which allows for faster reads and writes, which increases performance.
切分的好处（如分区一样）在于它可以压缩大型数据：单独的数据表在每个切分中相对较小，这样就可以支持更快速的读写速度，从而提高性能。
It would be far easier to build a bigger database server, and push off the need to rebuild your application to support the sharding of data.
使用更强大的数据库服务器要容易得多，而且不需要通过重新构建应用程序来支持分散的数据。
Jan notes that the technique can also be used to implement other data distribution strategies, such as sharding.
Jan提醒说这个技巧还可以用来实现其他的数据分布策略，例如分片(Sharding)。
Slice has extended OpenJPA implementation to support data partitions or sharding in a seamless manner.
Slice扩展了OpenJPA实现，使其能够无缝地支持数据分区。
Slice has extended OpenJPA implementation to support data partitions or sharding in a seamless manner.
Slice扩展了OpenJPA实现，使其能够无缝地支持数据分区。
应用推荐