{"id":29040,"date":"2015-11-01T22:12:36","date_gmt":"2015-11-01T16:42:36","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=29040"},"modified":"2017-01-23T22:34:56","modified_gmt":"2017-01-23T17:04:56","slug":"hazelcast-object-deserialization-with-distributed-query","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/hazelcast-object-deserialization-with-distributed-query\/","title":{"rendered":"#Hazelcast : Enhance throughput of Java apps performance by optimization of object deserialization and distributed query"},"content":{"rendered":"

Hazelcast is a popular solution for In-Memory Data Grid that is often used with Databases in order to improve performance of applications, to distribute data across servers, clusters and geographies and to manage very large data sets. Here’s a quick reference to\u00a0integrate\u00a0hazelcast with grails<\/a>\u00a0\u00a0.<\/p>\n

Since Hazelcast is a distributed system, we need to put serialized data into hazelcast.\u00a0\u00a0See\u00a0http:\/\/docs.hazelcast.org\/docs\/latest\/manual\/html\/serialization.html\u00a0for more information about object serialization & deserialization. Deserialization\u00a0of objects is expensive. Therefore you want to avoid it or optimize it as much as possible while working with Hazelcast .
\nFor example:<\/p>\n

(1)<\/strong> Use IMap.delete()<\/code> instead of IMap.remove()<\/code>, and IMap.set()<\/code> instead of IMap.put()<\/code>. These alternate methods don’t return a value and therefore cause less deserialization.<\/p>\n

(2) Choose an efficient Serialization method.<\/strong>
\n>><\/strong> When Hazelcast serializes an object into Data:<\/p>\n