What do you like best about the product?

Hazelcast first of all is a really great distributed data grid. You can use distributed collections out of the box like Map, Set, Queue for microservices replicas to share data or for caching purposes. Also, it is possible to take distributed locks to prevent doing the same work simultaneously. The Streaming framework Hazelcast Jet has many needful features and is very fast. Can be run separately from services or as a library. Supports automatic rebalancing and replication. Multiple network options to make a cluster such as multicasting or kubernetes support.

What do you dislike about the product?

It`s a little bit tricky to set up cluster in Kubernetes but it`s a matter of reading the documentation carefully. You should write serializers for objects yourself but it`s your payment for the size of the memory footprint of your cache. Poor search options in in-memory data structures.

What problems is the product solving and how is that benefiting you?

Distributed cache, distributed locking for microservices architecture. Stream processing of the big data.

Recommendations to others considering the product:

Great tool for distributed caches and for the stream processing