redka
Redis re-implemented with SQLite (by nalgeon)
Memcached
memcached development tree (by memcached)
redka | Memcached | |
---|---|---|
3 | 56 | |
2,768 | 13,236 | |
- | 0.9% | |
9.4 | 8.4 | |
3 days ago | 6 days ago | |
Go | C | |
BSD 3-clause "New" or "Revised" License | BSD 3-clause "New" or "Revised" License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
redka
Posts with mentions or reviews of redka.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-04-14.
-
Redis Re-Implemented with SQLite
I've decided to use the max connections approach for now.
[1]: https://github.com/nalgeon/redka/blob/main/internal/sqlx/db....
Memcached
Posts with mentions or reviews of Memcached.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-05-01.
-
System Design: Databases and DBMS
Memcached
- Redis Re-Implemented with SQLite
-
Best engineering interview question I've gotten
> Multiple clients racing can't be fixed.
Really? You can't think of a single way for multiple clients to operate on the same data without racing? (Here's a hint if you're still having trouble: https://github.com/memcached/memcached/wiki/Commands#cas.)
- Memcached 1.6.25 Release Notes
- Memcached 1.6.24 Release Notes
-
How to choose the right type of database
Memcached: A simple, open-source, distributed memory object caching system primarily used for caching strings. Best suited for lightweight, non-persistent caching needs.
-
Sieve is simpler than LRU
Oh, thank you! I didn't realize that LRU Maintainer Thread was more than an expiration reaper. When it was first being introduced that was its first responsibility as lazy expiration removal by size eviction meant dead entries wasted capacity. It was all work in progress when I had read about it [1] and talked to dormando, so it got fuzzy. The compat code [2, 3] might have also thrown me off if I only looked at the setting and not the usage. Its a neat variant to all of these ideas.
[1] https://github.com/memcached/memcached/pull/97
-
A Developer's Journal: Simplifying the Twelve-Factor App
stores session state in a session store like Memcached or Redis.
-
In-memory database Redis wants to dabble in disk
memcached has recently gained the ability to spill to disk: https://github.com/memcached/memcached/wiki/Extstore
we recently implemented this to grow our caches to >50TB
-
Django Caching 101: Understanding the Basics and Beyond
Django supports using Memcached as a cache backend. Memcached is a high-performance, distributed memory caching system that can be used to store cached data across multiple servers.