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 authorSep 28, 2012
Hazelcast Tip: Use map.set() instead of map.put()
The put() is the usual way for most of us to populate maps.
The Hazelcast IMap has an extra operation: set()
The difference of set() is that it does not return the old value.
That means a performance benefit especially if you use a mapstore.
So if you do not need the old value, it is always better to use set() for populating hazelcast distributed map.