Can you give some insights on why to avoid Hazelcast or friends for distributed system?
I can give my sample usages. I mainly used it for organizing the cluster automatically, like managing membership, server joining or leaving, maintaining the master server address list. With a distributed hash scheme like Soda, any member server can accept work from any client. Scaling out is very simple, just boot up a machine from an image. It would use Hazelcast to join the cluster and become available.
I also used it for distributing jobs, nice to able to say - queue these jobs and the distributed workers pick them up automatically.
I avoid using it for shared memory stuff, using it like Memcached. That's what Memcached, Redis, and friends are for.
I can give my sample usages. I mainly used it for organizing the cluster automatically, like managing membership, server joining or leaving, maintaining the master server address list. With a distributed hash scheme like Soda, any member server can accept work from any client. Scaling out is very simple, just boot up a machine from an image. It would use Hazelcast to join the cluster and become available.
I also used it for distributing jobs, nice to able to say - queue these jobs and the distributed workers pick them up automatically.
I avoid using it for shared memory stuff, using it like Memcached. That's what Memcached, Redis, and friends are for.