Efficient in-memory database, best when used next to a relation database
What do you like best about the product?
I like Hazelcast being configurable to auto back-up features of it. When one of your hazelcast instance is down, remaining instances in the cluster recovers those data from backup and continue working where it left.
What do you dislike about the product?
I can't think of anything I don't like about Hazelcast IMDG, maybe the pricing would be the worst side of it.
What problems is the product solving and how is that benefiting you?
Hazelcast is solving our caching problem and fastens the data access time. It also makes it possible to spend less time on managing instances of cache. The instances can discover each other and communicate as default.
Recommendations to others considering the product:
I used Hazelcast embedded to the services. However, stand-alone usage of Hazelcast might provide a better/more sustainable cluster.
There are no comments to display