What’s new in Hazelcast 3?

Hazelcast 3 is the biggest change that we have introduced to Hazelcast ever.  As Hazelcast grew with more and more features, we often felt that the inner architecture is no longer good enough to support those additions. It was almost impossible to introduce some of new features that community really wanted. So a decision made […]

Property Accessors

Here’s a short update:

At the moment there’s not much to tell but I’d found at lot of interest in properties support in Java and I’m glad to see people like the general idea.

The first discussion started mostly about how the syntax should look like and why defining a

Hazelcast Tip: Native Client versus Lite Member

There are two options to connect to Hazelcast cluster.

– Using native client
– Creating a lite member which is practically a node which does not store any data.
At first glance using lite member may seem more attractive as it knows all nodes and where any key-value pair is stored. But we see that in the long term native client is the more scalable and clean approach.
Here a table to summarize the difference between them:
       

.

     

.

     

.

     

.

  Native Client Lite Member

.

Performance There is an extra hop as client asks to a member where the data is. Better performance as it knows where data is.

.

Scalability More scalable as you can create any number of client without overhead to cluster operations. Not scalable, as each lite member becomes a node of the cluster that is an overhead for cluster operations.

.

Flexibility and Location Flexible, can be anywhere in LAN or WAN. It must be on the same data center even on the same RAC

.

Near Cache Currently not available Available

.

Distributed executor Can send tasks but cannot receive and execute Can send and receive taks