InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Google Contributes Data Partitioning Capability to Hibernate

Posted by Scott Delap on Mar 20, 2007

Sections
Architecture & Design,
Development,
Operations & Infrastructure
Topics
Java ,
Data Access
Tags
Hibernate
Three new top level Hibernate projects were released today: Validator, Search, and Shards.  Search and Validator are both promotions of existing work.  Shards which was contributed by Google is a horizontal partitioning solution built on top of Hibernate Core. From the press release:

Hibernate Shards, contributed by Google, offers critical data clustering and support for horizontal partitioning (also called sharding) to Hibernate. Now, customers can keep their data in more than one relational database for whatever reason-too much data or to isolate certain datasets, for instance-without added complexity when building and managing applications. Hibernate Shards is designed to encapsulate and reduce the complexity of building applications that work with sharded datasets.

"The ability to improve scalability by seamlessly distributing data across multiple databases is crucial for enterprise applications that transact against large or physically distributed datasets," said Google software engineer Max Ross. "We're pleased to contribute our implementation for horizontal partitioning to open source via Hibernate, and we look forward to working with the Hibernate team to further this technology."

Today also marks updated releases of Hibernate Annotations and Hibernate Entity Manager 3.3.0GA. Among the included features:
  • Improved support for legacy mapping, including better native SQL customization support and fetching strategies.
  • Out-of-the-box integration between all Hibernate components. Users have asked for flexibility of components so they can implement Hibernate in whichever manner suits their development. Now there's less configuration hassle so users can start developing right away.
  • Improved integration in third party environments such as IBM WebSphere, BEA WebLogic, and pure Java Persistence solutions.
wow by Jesse Kuhnert Posted
  1. Back to top

    wow

    by Jesse Kuhnert

    Thanks, google. If you've ever had to do it by hand you'll know it's nothing to sniff at. This is the kind of open source I want to see from google. Awesome. :)

Educational Content

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.

Max Protect: Scalability and Caching at ESPN.com

Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.

The Seven Deadly Sins of Enterprise Agile Adoption

Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.

Questions for an Enterprise Architect

Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?