We always have new ideas to solve data related problems.You will find some of these experiments here.
Hibernate OGM has not been kept up to date with the latest Hibernate ORM versionsand is not maintained anymore.If community members have interest in maintaining it, pleasecontact us.
Hibernate Shards has not been kept up to date with the latest Hibernate ORM versions.Some community members have interest in making it catch up.If you are interested,contact us.
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.
Sometimes the lawyers say "no" (or more likely, "NOOO!").
Whatever your reasons,talking to multiple relational databases inevitably complicates the development of your application.
Hibernate Shards is a framework that is designed to encapsulatesand minimize this complexity by adding support for horizontal partitioning to Hibernate Core.
Hibernate Shards allows you to continue using the Hibernate APIs you know and love:SessionFactory, Session, Criteria, Query.If you already know how to use Hibernate, you already know how to use Hibernate Shards.
Distribute data across your shards any way you want.Use one of the default strategies we provide or plug in your own application-specific logic.
Think your sharding strategy is never going to change? Think again.Adding new shards and redistributing your data is one of the toughest operational challenges you will faceonce you’ve deployed your shard-aware application.Hibernate Sharding supports virtual shards, a feature designed to simplify the process of resharding your data.
Hibernate Shards is licensed under the LGPL (Lesser GNU Public License)
Reference documentation ashtml,single page html orpdf.Javadoc.