choose when you need a standalone stream-processing engine and will provide external storage instead of using Hazelcast's built-in store.
Apache Flink
- 26.3k
- Java
- Apache-2.0
distributed in-memory data store and stream processing
Hazelcast is a Java distributed in-memory data platform that combines key-value storage and caching with stream processing, SQL, and real-time event-driven access.
Solves the same problem with a different architecture or at a different layer. Expect to rewrite the integration.
choose when you need a standalone stream-processing engine and will provide external storage instead of using Hazelcast's built-in store.
Apache Flink
choose when you want an enterprise Java in-memory data grid with Oracle support and do not need Hazelcast's integrated stream-processing layer.
Oracle Coherence Community Edition
An earlier or more limited way to do the job. Still the right call when you need something small, proven, or CPU-only.
choose when Redis/Memcached-protocol high-throughput caching is all you need and you do not need Hazelcast's JVM data grid or stream processing.
A modern replacement for Redis and Memcached
choose when you want a lightweight Go-embeddable distributed in-memory cache instead of a Java platform with stream processing.
Distributed, in-memory key/value store and cache. It can be used as an embedded Go library and a language-independent service.
choose when a lightweight Redis-protocol cache/data-structure server covers your real-time store needs and you will supply stream processing separately.
For developers, who are building real-time data-driven applications, Redis is the preferred, fastest, and most feature-rich cache, data structure server, and document and vector query engine.
choose when you need a .NET-friendly remote cache-store and can give up Hazelcast's stream-processing/SQL layer.
Garnet is a remote cache-store from Microsoft Research that offers strong performance (throughput and latency), scalability, storage, recovery, cluster sharding, key migration, and replication features. Garnet can work with existing Redis clients.
choose when you want a BSD-licensed Redis-compatible key-value store/cache and no Hazelcast-style compute or stream processing.
A flexible distributed key-value database that is optimized for caching and other realtime workloads.
These projects were analysed and named hazelcast among their alternatives. The relationship is not symmetric — how hazelcast rates them is a separate judgement, made when hazelcast is analysed in its own right.
calls hazelcast “Choose when you need a Java-based in-memory data grid with stream processing alongside caching.”
For developers, who are building real-time data-driven applications, Redis is the preferred, fastest, and most feature-rich cache, data structure server, and document and vector query engine.
calls hazelcast “choose when you need a Java in-memory data grid with stream processing and a broader data platform rather than a pure key-value cache.”
A flexible distributed key-value database that is optimized for caching and other realtime workloads.
calls hazelcast “Choose when you want embedded stream processing co-located with an in-memory data grid instead of a separate Flink cluster.”
Apache Flink
calls hazelcast “choose when you need a JVM distributed in-memory data grid with caching plus stream processing, not RESP-compatible”
Garnet is a remote cache-store from Microsoft Research that offers strong performance (throughput and latency), scalability, storage, recovery, cluster sharding, key migration, and replication features. Garnet can work with existing Redis clients.