High performance JPA with GlassFish and Coherence - Part 1
Join the DZone community and get the full member experience.Join For Free
Have you heard about Coherence before? Probably. It's one of those
famous in-memory grid solutions promising awesome fast data access and
unlimited space for your frequently used data. Some of its well know
competitors are Infinispan, Memcached and Terracotta Ehcache.
They are all great and the worst part with Coherence probably is, that
it is NOT open source. This is the first part of a four part series in
which I shortly explain the usage of Coherence together with GlassFish.
This one is intended to give you a brief overview of the possible
scenarios. The following ones will go into more details and describe the
configuration with concrete examples.
Why did I choose Coherence over any of the other ones? I love working with GlassFish and I was looking for a stable and easy integration with one of those in-memory grids for some data intensive use-cases recently. So the first place to look was the Oracle product stack. I was more or less driven by the idea that there has to be any kind of integration into EclipseLink which is the JPA 2.0 RI shipped with GlassFish. Especially since there is the new Cache API with JPA 2.0.
First research revealed a leak of information in that topic. Neither of the mentioned products does have any plugin or other integration with EclipseLink up to now. Even if EclipseLink has something called the "cache interceptor" framework which allows you to tie in 3rd party cache systems really easily, I was looking for a (probably supported) ootb solution. So I ended up looking at Coherence. Little remark: I am not the right person to ask about licensing or costs. All I do is use Coherence according to the OTN License.
What is Coherence?
Oracle Coherence is an in-memory data grid solution. You can scale mission-critical applications by using Coherence to provide very fast access to frequently used data. By automatically and dynamically partitioning data in memory across multiple servers, Coherence enables continuous data availability and transactional integrity, even in the event of a server failure. It is a shared infrastructure that combines data locality with local processing power to perform real-time data analysis, in-memory grid computations, and parallel transaction and event processing.
Strategies for JPA on the grid
All of the in-memory data grid solutions have a very simple put/get API. You issue something like:
to store your objects into the cache or get them back from the cache. Coherence would be responsible to persist everything into your Database (probably using EclipseLink). From an application point of view this seems like a very straight forward API to use. Let's call it the "JPA backed Caches". But it's only one of the three possible scenarios. The second is the L2 Cache approach for JPA which basically means your simply implement your JPA based application and plug in coherence in a second step. Third is combination of the first two and simply redirects all database operations to Coherence. All three have their positive points and of course drawbacks.
Products and Definitions
At this point in time it's best to look at the different products and names around. The JPA 2 RI is EclipseLink, which is part of the commercial offering from Oracle called TopLink. All the Coherence integration is part of the TopLink Grid product which also contains EclipseLink as JPA implementation.
1) JPA backed Caches
You can use the Coherence API with caches backed by a database mapped through JPA. The grid accesses relational data through JPA CacheLoader and CacheStore implementations. In this "traditional" Coherence approach, TopLink Grid provides CacheLoader and CacheStore implementations that are optimized for EclipseLink JPA. ( and ) which are both contained in the toplink-grid.jar file. Going this way, you use the standard JPA run-time configuration file persistence.xml and the JPA mapping file orm.xml. The Coherence cache configuration file coherence-cache-config.xml must be specified to override the default Coherence settings and define the CacheStore caching scheme.
I'll dive into this example with the next blog post which should be the second part in the series.
2) JPA L2 Cache
The Grid Cache configuration uses Coherence as the JPA shared (L2) cache.
Primary key queries attempt to get entities first from Coherence and, if unsuccessful, will query the database, updating Coherence with query results. Non-primary key queries are executed against the database and the results checked against Coherence to avoid object construction costs for cached entities. Newly queried entities are put into Coherence. Write operations update the database and, if successfully committed, updated entities are put into Coherence.
I'll explain this strategy with the third part in the series.
3) JPA L2 Cache with a JPA backed Cache
The Grid Entity configuration should be used by applications that require fast access to large amounts of fairly stable data and that perform relatively few updates In combination with Coherence as a L2 Cache using write-behind to improve application response time by performing database updates asynchronously. Read operations get objects from the Coherence cache. Write operations put objects into the Coherence cache, the configured L2 Cache performs write operations on the database.
I'll show you this example with the last part in the series.
Further Reading and Downloads:
TopLink Grid 11g (188.8.131.52.0)
Toplinkgrid Examples (OTN login required)
Opinions expressed by DZone contributors are their own.