JEjetbalsa·Apr 14, 2024
I've used SSDB[0] in the past for some really stupid large datasets (20TB)_and it worked really well in production
[0] https://github.com/ideawu/ssdb
In Redis re-implemented with SQLiteideawu
ssdb
C++2014–2024
ideawu / ssdb
ssdb
SSDB - A fast NoSQL database, an alternative to Redis
11Distinct people
16Mentions
0Explicit recommenders
8.3KGitHub stars
What to know before exploring
What it is
SSDB - A fast NoSQL database, an alternative to Redis
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
No other repository is repeatedly linked in the same discussions.
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 year16 dated mentions
Observed mentions: 2014-07-14 17:57:40 UTC to 2024-04-14 18:49:29 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 | 2 | 1 | 1 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 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 | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 5 | 3 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
16 sourcesAlso, comment out all `SAVE` to disable snapshotting so you can use the full machine RAM. Otherwise, you have to limit Redis to 50% RAM usage because Redis duplicates the dataset in memory when saving to disk, wasting half the machine's RAM. If you go over 50% RAM usage with snapshotting enabled you risk triggering bgsave error.
Finally, check out Redis-compatible alternatives that don't require the data set to fit in RAM. [0]
0: https://github.com/ideawu/ssdb
In Ways to shoot yourself in the foot with RedisAlso SSDB: https://github.com/ideawu/ssdb
In LMDB: The first version of Redis, written in Tcl (2009)> Or wanting to shift the architecture entirely to avoid using memory-bound Redis as a queue with an overflow risk.
I wanted to use SSDB[1] instead of Redis for that reason, but it doesn't support the necessary data structures.
[1] https://github.com/ideawu/ssdb
In Show HN: WakaQ - a Python distributed task queueI 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.
Tell HN: Memcached and Redis Considered Harmful
It's 2021 and we have extremely fast key-value lookups using LevelDB/RocksDB, but we're still using RAM-based caching tools [1] [2] [3]. It's time to consider RAM-based caching harmful, and start caching with SSDs for larger datasets and lower costs. For ex: SSDB [4]
[1] https://redis.io/
[2] https://memcached.org/
[3] https://news.ycombinator.com/item?id=29532552
[4] https://github.com/ideawu/ssdb#ssdb-vs-redis
6 points · Open discussionStop using RAM for caching, SSDs are just as fast now with LevelDB/RocksDB and can store a magnitude more data. Look into SSDB [1] instead of Memcached.
I know it's Redis, but it's basically the same as Memcached if you only use the key-value set/get commands.
See this blog post [2] and this Gophercon 2021 talk [3] for examples of it's use in production.
[1] https://github.com/ideawu/ssdb
[2] https://wakatime.com/blog/45-using-a-diskbased-redis-clone-t...
[3] https://www.youtube.com/watch?v=35eIxI_n5ZM&t=10533s
In Drop-In Replacement for MemcachedSSDB – A fast NoSQL database, an alternative to Redis
1 points · Open discussionHere it is the repo https://github.com/ideawu/ssdb
In KeyDB CEO Interview: Getting into YC with a Fork of RedisSSDB – A Redis compatible NoSQL database stored on disk
3 points · Open discussionWe're using a Redis alternative called SSDB [1] in production because the entire data set doesn't need to fit in RAM. This saves us thousands of dollars per month in server costs. Like you say, latency gains is nominal. The main reason I see alternative databases used is one missing key feature that's custom to a specific use case.
[1]: https://github.com/ideawu/ssdb
In A multithreaded fork of Redis that is fasterThis Redis-compatible alternative is also BSD licensed:
https://github.com/ideawu/ssdb
And it doesn't require the dataset fit in RAM.
In Redis will remain BSD licensedOr even better: using SSDB, a drop in replacement for Redis that scales to larger data sets.
https://github.com/ideawu/ssdb
In Faust: Stream Processing for PythonSSDB – A fast NoSQL database, an alternative to Redis
2 points · Open discussionSSDB – A fast NoSQL database, an alternative to Redis
2 points · Open discussionShowing the 15 most recent of 16 sources. Enable JavaScript to search and browse every indexed mention.