All geek questions in one place

Hibernate Distributed Layer 2 Cache Options

Not really a question, but I'm looking for comments / suggestions from anyone with experience using one or more of the following:

  • EhCache with RMI
  • EhCache with JGroups
  • Terracotta EhCache
  • Gigaspaces Grid

A bit of background: our applications are read only for the most part, but there is some user data that is read and written, and some of them are written (and can also be quite inaccurate). In addition, it would be nice to have tools that allow us to flush and fill the cache with an interval or administrative intervention.

Regarding the first option - are there any problems with the RMI overhead and Java serialization performance?

+3
source share
2 answers

I have been working with EhCache for Hibernate and for the application level cache since 3 years ago. We use it with RMI to invalidate the cache, and it works very well. If you use the cache for replication, you should take care of the graph of objects, it can become very heavy with high power ratios.

If you use EhCache for Hibernate, you can use it for the Query cache (this is a good improvement for read-only tables), and the table is modified, it automatically clears the cache. Using EhCache to cache collections is also a good idea to avoid aggregating subselects.

, EhCache, . .

, .

+2

Hazelcast, Coherence GemStone. . Hibernate. Hazelcast .

+3

Source: https://habr.com/ru/post/1747513/

More articles:


All Articles