Hazelcast 3.3.1

Open source clustering and highly scalable data distribution platform for Java
  1 Screenshot
Hazelcast Community Edition is an open source and highly scalable clustering data distribution platform for Java.

Hazelcast Community Edition is for you if you want to:
· share data/state among many servers (e.g. web session sharing)
· cache your data (distributed cache)
· cluster your application
· partition your in-memory data
· distribute workload onto many servers
· take advantage of parallel processing
· provide fail-safe data management

Hazelcast is pure Java. JVMs that are running Hazelcast will dynamically cluster. Although by default Hazelcast will use multicast for discovery, it can also be configured to only use TCP/IP for enviroments where multicast is not available or preferred. Communication among cluster members is always TCP/IP with Java NIO beauty.

Default configuration comes with 1 backup so if one node fails, no data will be lost. It is as simple as using java.util.{Queue, Set, List, Map}. Just add the hazelcast.jar into your classpath and start coding.

Main features:

  • Distributed implementations of java.util.{Queue, Set, List, Map}
  • Distributed implementation of java.util.concurrency.locks.Lock
  • Distributed implementation of java.util.concurrent.ExecutorService
  • Distributed Topic for publish/subscribe messaging
  • Transaction support and J2EE container integration via JCA
  • Dynamic HTTP session clustering
  • Support for cluster info and membership events
  • Dynamic discovery
  • Dynamic scaling to hundreds of servers
  • Dynamic partitioning with backups
  • Dynamic fail-over

last updated on:
September 30th, 2014, 12:50 GMT
file size:
56.3 MB
license type:
developed by:
Hazelcast Inc
operating system(s):
Mac OS X
binary format:
Home \ Internet Utilities
Download Button

In a hurry? Add it to your Download Basket!

user rating



Rate it!
What's New in version 3.3
  • New Features:
  • Heartbeat for Java client: Before this release, a Java client could not detect a node as dead, if the client is not trying to connect to it. With this heartbeat feature, each node will be pinged periodically. If no response is returned from a node, it will be deemed as dead. Main goal of this feature is to decrease the time for detection of dead (disconnected) nodes by Java clients, so that the user operations will be sent directly to a responsive one.
  • Tomcat 6 and 7 Web Sessions Clustering: Please see Session Replication.
  • Replicated Map implemented: Please see Replicated Map
read full changelog

Add your review!