Max Ross and Maulik Shah were
part of a core group that worked on the recently open sourced Hibernate Shards project.
In the podcast you will learn:
What sharding
is and what it means in the world of Hibernate
How the word "shards" is
common at Google (the equivalent of "smurf" in The Smurfs)
Why you would
want to shard your data to give you increased scalable performance
How the
Hibernate Shards project doesn't mess with the core APIs, allowing you to add sharding
unobtrusively
What you need to think about if you want to
shard your data, and how you can design a schema that has a dimension that is easily sharded.
This includes designing without complex relationships.
How you
could create a crazy project that shards data across multiple databases
(as in, one mysql, one Oracle), but that would be crazy
The various
strategies to define how you retrieve your objects across the distributed data
store
How this compares with horizontal partitioning at the database level
itself (e.g. new features in MySQL, PostgreSQL, and others)
