Question

I’m using JPA and I am using second-level cache for all the reference entities.
Everything’s working well, I can get the entities from second-level cache is they were already been selected before.

Now, I have two applications, they both use the same database (so they both use the same table, values, etc).
1.The read-only application just read data from database, it doesn’t modify the database at all. Therefore, I choose the “READ_ ONLY” concurrency strategy for the second-level cache, aiming at a better performance.
2.The read-write application read and write as well the data of database, it modify the database. Consequently, I have to choose the “READ_ WRITE” or “NONSTRICT_ READ_ WRITE” concurrency strategy for the second-level cache.

However, the concurrency strategy is assigned in the annotation of each entity class, so I cannot change it programatically. (I don’t use class mapping files for JPA, so I can’t use two mapping files, each for a different concurrency strategy for the same entity class.)

My Question is, is there a good way to change the concurrenty strategy of the second-level cache on the fly according to my 2 different applications?

Answer 1

So Therefore, I think the current solution is to replace all the annotations of each entities with Hibernate mapping files, so that for different deployment (application as well), we could use different Hibernate mapping files.