Community Archives | Page 3 of 15 | Hazelcast

Hazelcast Jet 3.2 is Released

by Can Gencer — Oct 23, 2019

We are excited to introduce Hazelcast Jet 3.2, the latest version of Hazelcast’s batch and stream processing platform. We’ve added...

Announcing the First Release of Hazelcast Jet Extension Modules

by Emin Demirci — Jul 17, 2019

We are excited to announce the new repository for extension modules of Hazelcast Jet. This repository will be home for...

The One Beam to Rule Them All

by Greg Luck — Jun 26, 2019

Unbounded, unordered, global-scale datasets are increasingly common in day-to-day business – IoT sensor network data streams, mobile usage statistics, large...

Rolling Upgrade Hazelcast IMDG on Kubernetes

by Rafal Leszko — Jun 25, 2019

Hazelcast IMDG is tightly integrated into the Kubernetes ecosystem thanks to the Hazelcast Kubernetes plugin. In previous blog posts, we...

Red Herring Recognizes Hazelcast as Top 100 Award Winner

by Matt Wolpin — May 23, 2019

Last week, Hazelcast earned a coveted spot on the list of Red Herring’s Top 100 North America private technology companies....

Hazelcast Jet 3.0 is Released

by Can Gencer — Apr 16, 2019

We are happy to announce the first General Availability release of Hazelcast Jet, two years after our first public release...

Announcing Hazelcast Cloud GA

by Enes Akar — Mar 26, 2019

Today, we are announcing the general availability of Hazelcast Cloud, our new managed service. I remember the day about 9-years-ago...

In-Memory Data Grids Popularity Trend Continues Upward

by David Brimley — Mar 14, 2019

The past year has seen in-memory data grids (IMDG) continue to gain traction with the development community and large organisations...

Executing Machine Learning at Scale and Speed

by Dan Ortega — Jan 31, 2019

One of the current hot topics driving the in-memory domain is the potential associated with the application of Machine Learning...

LockSupport.parkNanos() Under the Hood and the Curious Case of Parking

by Jaromir Hamala — Jan 28, 2019

When a colleague of mine was running some experiments, he noticed `LockSupport.parkNanos()` would either return almost immediately or in roughly...

How can we help?