choose for a C++-based Redis/Memcached-compatible server with high throughput and lower memory when you don't need .NET
A modern replacement for Redis and Memcached
- 31.0k
- C++
- NOASSERTION
remote cache-store / Redis-compatible key-value store
Garnet is a high-performance remote cache-store from Microsoft Research that uses the RESP wire protocol, making it compatible with existing Redis clients.
Same problem, same approach. Swapping one for another is a config change, not a rewrite.
choose for a C++-based Redis/Memcached-compatible server with high throughput and lower memory when you don't need .NET
A modern replacement for Redis and Memcached
choose for a community-maintained Redis-compatible cache with battle-tested C code and the open Redis ecosystem
A flexible distributed key-value database that is optimized for caching and other realtime workloads.
choose for a lightweight C++ Redis-compatible server if you prefer that codebase/community over .NET
Pikiwidb is a Redis-Compatible database developed by Qihoo's infrastructure team.
choose for the canonical Redis server when you want the most mature, feature-rich data structures and ecosystem
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.
Solves the same problem with a different architecture or at a different layer. Expect to rewrite the integration.
choose when you need a JVM distributed in-memory data grid with caching plus stream processing, not RESP-compatible
Hazelcast is a unified real-time data platform combining stream processing with a fast data store, allowing customers to act instantly on data-in-motion for real-time insights.
choose for an embedded Go distributed cache with its own protocol when you don't need Redis wire compatibility
Distributed, in-memory key/value store and cache. It can be used as an embedded Go library and a language-independent service.
An earlier or more limited way to do the job. Still the right call when you need something small, proven, or CPU-only.
choose for a lightweight embedded Redis-like store on SQLite when you need durability without a standalone server
Redis re-implemented with SQL
These projects were analysed and named garnet among their alternatives. The relationship is not symmetric — how garnet rates them is a separate judgement, made when garnet is analysed in its own right.
calls garnet “Choose when you want a Redis-compatible cache store with Microsoft's high-performance and cluster features.”
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 garnet “Redis-compatible remote cache-store with high performance; choose if you prefer a C# implementation and need a drop-in Redis replacement”
A modern replacement for Redis and Memcached
calls garnet “C# Redis-compatible cache-store from Microsoft Research, choose if you prefer a managed-language server or need a highly scalable cache-store with modern design.”
A Multithreaded Fork of Redis
calls garnet “choose when you want a .NET-based high-performance remote cache-store with Redis protocol support, especially for Windows-centric deployments.”
A flexible distributed key-value database that is optimized for caching and other realtime workloads.
calls garnet “Choose it when you want a C#/.NET cache-store speaking Redis/Memcached protocols with strong throughput.”
SSDB - A fast NoSQL database, an alternative to Redis
calls garnet “choose when you need a .NET-friendly remote cache-store and can give up Hazelcast's stream-processing/SQL layer.”
Hazelcast is a unified real-time data platform combining stream processing with a fast data store, allowing customers to act instantly on data-in-motion for real-time insights.