[quote]Hibernate Shards
You can’t always put all your relational data in a single relational database.
Sometimes you simply have too much data. Sometimes you have a distributed deployment architecture
(network latency between California and India might be too high to have a single database). There might
even be non-technical reasons (a potential customer simply won’t do the deal unless her company’s data lives in its
own db instance). Whatever your reasons, talking to multiple relational databases inevitably complicates
the development of your application. Hibernate Shards is a framework that is designed to encapsulate and
reduce this complexity by adding support for horizontal partitioning on top of Hibernate Core. Simply put,
we aim to provide a unified view of multiple databases via Hibernate.[/quote]
[url]http://www.info-sys.cn/blog/index.php/archives/16[/url]
You can’t always put all your relational data in a single relational database.
Sometimes you simply have too much data. Sometimes you have a distributed deployment architecture
(network latency between California and India might be too high to have a single database). There might
even be non-technical reasons (a potential customer simply won’t do the deal unless her company’s data lives in its
own db instance). Whatever your reasons, talking to multiple relational databases inevitably complicates
the development of your application. Hibernate Shards is a framework that is designed to encapsulate and
reduce this complexity by adding support for horizontal partitioning on top of Hibernate Core. Simply put,
we aim to provide a unified view of multiple databases via Hibernate.[/quote]
[url]http://www.info-sys.cn/blog/index.php/archives/16[/url]