Category: How-to

This category is for posts that contain or link to how-tos for various methodologies and tools in the Hazelcast ecosystem.

Hazelcast for Go Getters

Know “Go” but don’t know about “Hazelcast” ? Know “Hazelcast” but don’t know about “Go” ? This tutorial gets you going with both together, in a follow-along style, assuming you only know one of the two. Hello World Naturally, this…

How to Integrate Guice with Hazelcast IMDG

Volkan Yazici recently published this blog post with the title, “Guice Integration in Hazelcast“. In this post, Volkan gives a short tutorial on integrating Guice with your Hazelcast IMDG project. For many occassions I find the distributed ExecutorService of Hazelcast…

Priority Queueing Using the SPI

Hazelcast provides distributed queues, an implementation of java.util.concurrent.BlockingQueue. However, an implementation of java.util.concurrent.PriorityBlockingQueue is not yet provided. In this example, we’ll see how to write this yourself, using Hazelcast’s SPI (Service Provider Interface). (Note: this is just an example, deliberately…

Deploying Hazelcast Jet

Deploying Hazelcast Jet This guide provides a basic introduction for deploying and operating a successful Hazelcast Jet installation. We plan to make this guide the first in a series of posts about deploying Hazelcast Jet. This will be a near…

Enabling SSL/TLS for Node.js Hazelcast IMDG Client

The Hazelcast IMDG Node.js client package supports certificate based authentication and encryption. This article looks at how to enable certificate based authentication and encryption for Node.js hazelcast client. For continuity it is recommended to go through the previous blog on…

Scale Big or Go Home

This post is syndicated from 7erry’s performance blog. Original post here. Scaling an application normally means you have a successful application and there is lots of demand. Unfortunately that demand can be immediate (within seconds / minutes) instead of spread…

Enabling Near Cache in Node.js Hazelcast Client

This post originally appeared on Riaz/Mohari’s GitHub page. See the original post here. Remote calls are expensive, it impacts performance. If an application has to make a remote call every time it process a request its performance can be improved…