This short video explains why companies use Hazelcast for business-critical applications based on ultra-fast in-memory and/or stream processing technologies.
Stream processing is a hot topic right now, especially for any organization looking to provide insights faster. But what does it mean for users of Java applications, microservices, and in-memory computing?
In this webinar, we will cover the evolution of stream processing and in-memory related to big data technologies and why it is the logical next step for in-memory processing projects.
Now, deploying Hazelcast-powered applications in a cloud-native way becomes even easier with the introduction of Hazelcast Cloud Enterprise, a fully-managed service built on the Enterprise edition of Hazelcast IMDG. Can't attend the live times? You should still register! We'll be sending out the recording after the webinar to all registrants.
No posts were found matching that criteria.
As we saw in part 1, it took 2+ minutes, on my laptop, to run an aggregation across 6+ million crime cases. However, since Hazelcast is cluster library, it only makes sense to take advantage of that. Let’s run this on a 3-node cluster. That will require a few code changes to CrimeNode: First, we […]
In this post we’ll take a look at the built-in aggregations in the Scala API. I was looking at publicly available data sets to run some analysis on, and a good choice seemed the Chicago Crime statistics, a data set that includes all crime cases since 2001. I chose the CSV download, which unfortunately is […]
A pre-release alpha version of the Scala API for Hazelcast has been released and is available on Github. It’s a “soft” API, i.e. it expands the Java API rather than replace it. The Scala API also adds built-in distributed aggregations, and IMap join capability. The Scala API targets version 3.6 of Hazelcast. Key features The […]
With Hazelcast there’s a plethora of ways to do serialization. Personally, I prefer to use either ByteArraySerializer or StreamSerializer, for a couple of reasons: They facilitate separation of concerns, i.e. the serialization code is separate from the class itself. Because they facilitate separation of concerns, there’s no required dependency on Hazelcast in the actual classes […]