Oracle Coherence Review

Customer Facing Application response time has improved. The error and exception handling is not that great as it can be difficult to debug issues.


Valuable Features

As well as using HotCache to synchronise a Coherence cache with database tables in real-time, it can also be used to warm the cache by loading an initial dataset. The nice thing about this approach is that cache warming is just an extension to the setup for cache synchronisation.

Improvements to My Organization

The Customer Facing Application response time has been improved 95%. Also, in the releases the Portal does not goes down as the data is being pulled from the Cache not from the Database.

Room for Improvement

Monitoring API needs to be improved and needs to be user friendly. Also, the error and exception handling is not that great as it can be difficult to debug issues.

Use of Solution

We have been using this solution for five years.

Deployment Issues

The GAR file naming convention.

Stability Issues

There have been issues in the cache configuration file in older versions, and a nodes eviction and timeout error.

Scalability Issues

To add additional capacity, the cluster has to be fully recycled and that cause the down time of the environment.

Customer Service and Technical Support

Oracle Customer Support works when we escalate the issue, otherwise first level support is not that good.

Initial Setup

The latest version is straightforward, as there is lots of configuration done through the WebLogic console.

Implementation Team

We implemented it ourselves. Before implementation, review the requirements thoroughly because if the cache sizing is not correctly defined it creates a major bottleneck. The size of the JVM depends on the size of cache.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest
Sign Up with Email