Comments on: Hazelcast Hot Cache with Striim https://piotrminkowski.com/2017/08/09/hazelcast-hot-cache-with-striim/ Java, Spring, Kotlin, microservices, Kubernetes, containers Sat, 12 May 2018 14:36:07 +0000 hourly 1 https://wordpress.org/?v=6.9.1 By: Up-to-Date Cache With EclipseLink and Oracle - Devoted To The Code https://piotrminkowski.com/2017/08/09/hazelcast-hot-cache-with-striim/#comment-386 Sat, 12 May 2018 14:36:07 +0000 https://piotrminkowski.wordpress.com/?p=5421#comment-386 […] One of the most useful features provided by ORM libraries is a second-level cache, usually called L2. An L2 object cache reduces database access for entities and their relationships. It is enabled by default in the most popular JPA implementations like Hibernate or EclipseLink. That won’t be a problem unless a table inside a database is not modified directly by third-party applications, or by the other instance of the same application in a clustered environment. One of the available solutions to this problem is an in-memory data grid, which stores all data in memory, and is distributed across many nodes inside a cluster. Such a tool like Hazelcast or Apache Ignite have been described several times in my blog. If you are interested in one of that tools I recommend you read one of my previous article about it: Hazelcast Hot Cache with Striim. […]

]]>
By: Up-to-date cache with EclipseLink and Oracle – Piotr's TechBlog https://piotrminkowski.com/2017/08/09/hazelcast-hot-cache-with-striim/#comment-385 Fri, 23 Mar 2018 15:30:15 +0000 https://piotrminkowski.wordpress.com/?p=5421#comment-385 […] One of the most useful feature provided by ORM libraries is a second-level cache, usually called L2. L2 object cache reduces database access for entities and their relationships. It is enabled by default in the most popular JPA implementations like Hibernate or EclipseLink. That won’t be a problem, unless a table inside a database is not modified directly by third-party applications, or by the other instance of the same application in a clustered environment. One of the available solutions to this problem is in-memory data grid, which stores all data in a memory, and is distributed across many nodes inside a cluster. Such a tools like Hazelcast or Apache Ignite has been described several times in my blog. If you are interested in one of that tools I recommend you read one of my previous article bout it: Hazelcast Hot Cache with Striim. […]

]]>