HAhackerdad·Mar 29, 2024
Netflix created a fully peer to peer distributed Redis compatible DB
https://github.com/Netflix/dynomite
In The race to replace RedisNetflix
dynomite
C2014–2024
Netflix / dynomite
dynomite
A generic dynamo implementation for different k-v storage engines
14Distinct people
17Mentions
0Explicit recommenders
4.2KGitHub stars
What to know before exploring
What it is
A generic dynamo implementation for different k-v storage engines
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- tencent/tendis · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year17 dated mentions
Observed mentions: 2014-11-03 22:07:16 UTC to 2024-03-29 15:25:16 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 5 | 1 | 4 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
17 sourcesI thought you'd never ask:
- KeyDB (https://keydb.dev)
- Pelican Cache (https://www.pelikan.io/)
- Tendis (https://github.com/Tencent/Tendis)
- SSDB (https://github.com/ideawu/ssdb)
- Dynomite (https://github.com/Netflix/dynomite/)
- Dragonfly (https://github.com/dragonflydb/dragonfly)
- Skytable (https://github.com/skytable/skytable)
- Tidis (https://github.com/yongman/tidis)
- Anna (https://github.com/hydro-project/anna)
- Skyhook (https://github.com/aerospike/skyhook)
And some which are kinda dead but still interesting -- redis is the kind of workload that does actually become feature complete so these are still usable in my mind though maybe not first choice:
- ledisdb (https://github.com/ledisdb/ledisdb)
- Codis (https://github.com/CodisLabs/codis)
- xcodis (https://github.com/ledisdb/xcodis)
I'm planning on doing a comparison with t
Read the rest
hese at some point, because they're fascinating (all these projects go off in subtly different directions, I'll spare you the details), but here's a recent comparison someone else did:
https://news.ycombinator.com/item?id=31796311
Basically, redis compatibility is like step 1 for any KVS that wants to seem at least a little usable/real-world-focused so you get so many cool entrants.
I don't really personally keep up with redis for the stream use-case -- it's a great use for redis but that doesn't really make/break for me usually.
Does anyone have any experience with these other Redis clones? I need to write a benchmark on these someday (the outline for the blog post is already written), but have restricted my yak shaving recently:
- https://github.com/Tencent/Tendis
- https://github.com/Netflix/dynomite
On a separate note, was FLASH (as in "flash memory") supposed to be an acronym? I've never seen people treat it as an acronym before.
In KeyDB CEO Interview: Getting into YC with a Fork of Redis> I'm just waiting for the day they can make the database immutable. It'll probably look something like git.
Netflix had immutable databases back in 2012. I mean, as close as you can get I suppose. We could lose 1/3 of the nodes and keep running normally, and lose 2/3 and keep reading.
It was built with Cassandra and based on the Dynamo model.
There was also an open source, fully in memory database with the same reliability: https://github.com/Netflix/dynomite
In Erase your darlings: immutable infrastructure for mutable systemsFollowing research papers from academia also explored similar problem:
1) BESPOKV: Application Tailored Scale-Out Key-Value Stores
http://people.cs.vt.edu/~butta/docs/sc18-bespokv.pdf
2) ClusterOn: Building Highly Configurable and Reusable Clustered Data Services using Simple Data Nodes
http://people.cs.vt.edu/~butta/docs/hotstorage16-clusteron.p...
DynomiteDB from Netflix allowed to scale singe server NoSQL stores. https://github.com/Netflix/dynomite.
In Technical Challenges Developing a Distributed SQL Databasei'm curious. which one netflix is currently using evcache or dynomite (https://github.com/Netflix/dynomite) ?
In Caching at Netflix: The Hidden Microservice (2016) [video]twemproxy is not the best piece of software when it comes to maintenance of code quality. But it works reliable. We are still using twemproxy and we are maintaining our own fork of it. This fork often has changes from us, like bugfixes or introducing new redis commands that are not supported yet.
Every bug we fix we apply this as a PR.
A few PRs from the repository we have cherry-picked internally and deployed.
But we have also a few issues with it like this one here: https://github.com/twitter/twemproxy/issues/442 or live reconfiguration would be a nice feature.
Think about it if you really need this, because it is not only fun.
A few pain points:
* Deployments of new configs and restarting twemproxy on your server farm
* New redis version with new commands? Extend twemproxy for those command support
I don't now any _real_ alternative to
Read the rest
it, right now.
I know from https://github.com/Netflix/dynomite which is a twemproxy fork.
When we had only memcached and no redis (we are using both with twemproxy), then we would try https://github.com/facebook/mcrouter from facebook. But it is specialized on memcached.
If you come up with an alternative, please let me know.
It's the full Redis API and protocol. See https://github.com/Netflix/dynomite/blob/dev/notes/redis.md for a list of all supported Redis features.
The benefit of Dynomite's support for the Redis API + protocol is a.) you can use any Redis client and b.) the same code can be used for standalone Redis on your laptop and on a distributed Dynomite cluster.
In Show HN: SummitDB – In-Memory NoSQL DBhttps://github.com/Netflix/dynomite
Dynomite for production proven, limitless scale for Redis.
Provides ability to Redis for both in-memory and on-disk workloads.
Dynamo-inspired linearly scalable, shared nothing multi-master architecture. Pairs well with Cassandra.
Supports pluggable backends (ex. RocksDB).
Been in production 2+ years. One of the larger clusters handles over 3.6 million sustained ops/sec in production, every day.
In Show HN: SummitDB – In-Memory NoSQL DBThat's a good idea. At the very least add a note about it in the mean time maybe. BTW as a caching-only system redis can scale exactly like memcache if your client supports it. I did this in one project and it worked great.
EDIT: Also, it might be too niche, but you can also have a look at redis+dynomite, which makes redis behave like a distributed database. https://github.com/Netflix/dynomite
In NoSQL Databases: A Survey and Decision GuidanceIf you use Redis, you should try out Dynomite at http://github.com/Netflix/Dynomite. It can provide HA for Redis servers
In January 28th Incident Report> when they were the only SSD option available -- they beat the crap out of spinning ephemeral disks.
No doubt!
What sort of stateful storage are you using on those EBS volumes?
If you're doing key/value, you might want to check out https://github.com/Netflix/dynomite
It turns redis into a dynamo-like key value store that might bootstrap your transition.
In Tarsnap performance issues in late March, most of AprilSetup and Installation Wiki - https://github.com/Netflix/dynomite/wiki/Getting+Started#set...
In Dynomite – Making Non-Distributed Databases Distributednitpick, the code check for NULLs at a low level but misses checking NULLs at higher levels like here:
https://github.com/Netflix/dynomite/blob/master/src/dyn_dnod...
In Dynomite – Making Non-Distributed Databases DistributedShowing the 15 most recent of 17 sources. Enable JavaScript to search and browse every indexed mention.