A newer kid on the block is hazelcast. I’ve been playing with it and it is amazingly simple to use and configure.
As far as I can see there shouldn’t be any conflict between Gigaspaces and hazelcast as hazelcast doesn’t have any dependencies i.e. no jgroups.jar etc
Hazelcast:
- A mutual exclusion (lock), yep implementation of
java.util.concurrency.locks.Lock
- Automatic lock release after a certain timeout, yep all locks are released if a member leaves the cluster
- Java implementation, yep
- Nice to have: .Net implementation, nope is a pure java solution, might be possible to port to j#
- If it’s free: Deadlock detection / mitigation, nope no effort is made my Hazelcast to handle this
- Easy deployment, it’s a single jar with a single config file, deployed as part of your application, no additional processes are required