High-level design of an ADO.NET sharding library.
NETshardinglibrary的高层次设计。
Next, I need to verify that my sharding implementation works.
接下来，我需要验证我的切分实现可以工作。
As of now, sharding framework cannot be used with HQL. It can only be used with SQL.
到目前为止，分片框架不能用于HQL，它只能用于SQL。
The sharding engine described above USES the sharding strategy provided by the application.
上面描述的分片引擎使用应用程序提供的分片策略。
Clearly, you'll need to fully consider a sharding strategy before you set up your database.
很明显，在建立数据库前必须全面考虑切分策略。
In the right situation, sharding could be key to unlocking scale and speed in a traditional RDBMS.
如果能够正确实现，切分可以用于解决传统RDBMS规模和速度问题。
Slice has extended OpenJPA implementation to support data partitions or sharding in a seamless manner.
Slice扩展了OpenJPA实现，使其能够无缝地支持数据分区。
Microsoft will release SQL Azure Federations which will support sharding at the database level in 2011.
微软将在2011年发布SQLAzureFederations，它将支持数据库级别的分片。
Jan notes that the technique can also be used to implement other data distribution strategies, such as sharding.
Jan提醒说这个技巧还可以用来实现其他的数据分布策略，例如分片(Sharding)。
As I mentioned earlier, sharding forces you to be keenly aware of primary keys, as you'll manage them yourself.
如我之前提到的那样，切分迫使您重视主键，因为您将需要亲自管理这些主键。
Database sharding refers to the horizontal partitioning of a database with each individual partition called a shard.
数据库分片是指对数据库进行水平分区，其中每个分区称为一个碎片。
There's a lot of things I can say about using caching, sharding, and other techniques to take load off the database.
当然你可以说出许多技巧来降低数据库的负载，比如利用缓存，数据分片等等。
That is, rather than splitting up a table into smaller chunks, sharding splits up an entire database into smaller chunks.
也就是说，切分不是将数据表分割成小块，而是将整个数据库分割成小块。
And because sharding is done at the application layer, you can do it for databases that don't support regular partitioning.
而且因为切分是在应用程序层面进行的，您可以对不支持常规分区的数据库进行切分处理。
Unlike other sharding solutions, Slice does not require adding any extra column to the existing schema to enable partitioning.
与其他的分区解决方案不同，Slice并不需要向现有模式中添加任何额外的列以支持分区。
This month, I'll use this familiar example to introduce a practical sharding strategy, then implement it in Hibernate Shards.
本月，我将继续使用这个熟悉的示例介绍一种实用的切分技术，然后在HibernateShards中对其进行实现。
WebSphere CloudBurst also includes an image repository, built into the appliance, which leverages encryption and sharding technologies.
WebSphereCloudBurst还包含一个内置到设备中的映像库，该库利用了加密和碎片技术。
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.
在微软的分片模式中，“分片键”用于将数据映射到特定的分片上，后者就是一个数据实体的主键。
Regardless, clustering, replication, and sharding each have pros and cons that should be weighed heavily before embarking on an individual strategy.
无论如何，集群、复制和分片都具有优缺点，在开始采用一种具体战略时应该认真权衡它们。
Standard JPA has no effective means of dealing with sharding or portioning as the specification implicitly assumes a single database as the repository.
标准JPA没有处理分区或分配的有效方式，因为规范已经隐式地假定单个数据库作为存储库。
Allows existing SaaS applications which use Hibernate, but do not yet need sharding, to adopt the solution without major refactoring if and when they do reach this stage.
允许使用Hibernate、但尚不需要分片的SaaS应用程序采用解决方案，而无需重大重构，前提是它们确实达到了这个阶段。
Because sharding isn't a native database technique - that is, you must implement it in your application - you'll need to map out your sharding strategy before you begin.
因为切分不是一项本地数据库技术—也就是说，必须在应用程序中实现—在开始切分之前需要制定出您的切分策略。
Database sharding provides many advantages, such as faster reads and writes to the database, improved search response, smaller table sizes, and distribution of tables based on need.
数据库分片提供许多优势，比如对数据库的更快读写、改进的搜索响应、更小的表格尺寸以及对表格的按需分配。
We will address the database scaling issues of SaaS applications using Hibernate Shards, which is an extension of Hibernate, and makes available the features of sharding to Hibernate users.
我们将使用HibernateShards (Hibernate的一个扩展)解决SaaS应用程序的数据库扩展问题，并向Hibernate用户提供分片的功能。
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.
切分的好处（如分区一样）在于它可以压缩大型数据：单独的数据表在每个切分中相对较小，这样就可以支持更快速的读写速度，从而提高性能。
Sharding: a test drive with easyb.
切分：使用easyb的测试驱动。
Sharding, an offshoot of database partitioning, isn't a native database technique - it happens at the level of the application.
切分是数据库分区的一个分支，但是它不是本地数据库技术—切分发生在应用程序级别。
Sharding also conceivably improves reliability, because even if one shard unexpectedly fails, others are still able to serve data.
切分还可以改善可靠性，因为即便一个切分意外失效，其他切分仍然可以服务数据。
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 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.
切分对于绑定于关系基础架构、无法继续升级硬件以满足大量可伸缩数据存储要求的组织来说是一个非常成本高效的决策。
应用推荐