By Enes Akar
Co-founder & CTO, Hazelcast Cloud
Enes was one of the early developers of Hazelcast. He joined the company in 2011 with a passion for making distributed computing incredible simple. From 2012 to 2017, he headed the engineering team as VP of Engineering. Since 2017, he has led the development of Hazelcast Cloud, which is enterprise-grade Hazelcast software as a fully managed service in the cloud. Prior to joining Hazelcast, Enes worked in software development and software engineering at telecommunications companies, including Alcatel-Lucent and Ericsson. He holds a Bachelor of Science in Computer Engineering and an MBA from Bogazici University, Istanbul.
View all blogs by the authorDec 26, 2012
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 a member where the data is. | Better performance as it knows where data is. |
|
. |
Scalability | More scalable as you can create any number of clients without overhead to cluster operations. | Not scalable, as each lite member becomes a node of the cluster it is an overhead hit 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 tasks |
