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 5, 2012
Hazelcast Tip: Use IMap.lock or ILock.lock?
When you call mapLocks.unlock(theKey), your lock is auto-garbage-collected. This is simpler, faster and cleaner.
For ILocks, you have to call destroy as all ILock objects are kept in memory.
If you don’t have lots of locks and you want to follow the j.u.c.Lock interface then you can use ILock otherwise IMap is nicer.