TopLinkVsHibernate

Read TopLink Product Manager's answer below.

TopLink and Hibernate appear very similar when comparing feature lists and rudimentary investigations. What you will find when you dig in further is that TopLink has some distinct advantages when it comes to:

1. Performance - TopLink's default shared cache lends itself to higher performance gains on read-only and read-mostly scenarios. This does introduce a more explicit transaction model (UnitOfWork) but the gains are worth it. This model evolved over years of working with large enterprise customers.

2. Scalability - TopLink's specialized cache and cache coordination lends itself to highly concurrent applications relying on the shared relational database for ultimate concurrency versus a middle tier locking model for distributed caching. The cache settings are configurable per entity type so you have great flexibility in how you wish to leverage TopLink's cache in a cluster.

3. Development Tool Productivity - Although we do support defining your meta-data in XML or code the use of the mapping editors (Workbench and JDeveloper) not only provide initial productivity gains but also necessary diagnostics for model evolution in an agile development environment. As the models change, as they typically do, the mapping editors will identify dependent mappings, queries, and other runtime properties that are effected by the model and corresponding changes to the mappings. This is a critical difference versus debugging an enormous set of XML config files through the use of runtime exceptions.

4. Flexibility - Although Hibernate 3 has addressed some of inflexibility in its mappings TopLink still offers many more mappings and customizations of these mappings. If you are using the Oracle DB then support for hints, hierarchical queries, XDB XML Type with query constructs, Object-Relational database types with queries, many SQL extended function and types (TIMESTAMP*, NCLOB, ...), excellent support for complex stored procedures and functions, as well as support of Virtual Private Database will definitely be key factors in your comparison.

I firmly believe that TopLink is a superior solution across the key aspects of ORM. The issue of cost and Hibernate being 'good enough' is typically where people lean towards Hibernate. JBoss's business model is based around support and services. Even they will tell you that you should have support in place putting a Hibernate system into production. I believe what you will find when you get a quote for support or services from JBoss that in the end TopLink is significantly cheaper and is included for free with any edition of the Oracle Application Server.

See Also

Read forum:277852, forum:290294.