4 ms·
What are the project goals? I assume it's a drop-in replacement for Redis that is supposed to be better in certain cases? If yes, then what cases do you have in
by sesm 3y ago
What are the project goals?
I assume it's a drop-in replacement for Redis that is supposed to be better in certain cases? If yes, then what cases do you have in mind?
- nalgeon 3y agoThe goal is to have a convenient API to work with common data structures, with an SQL backend and all the benefits it provides. Such as: — Small memory footprint even for large datasets. — ACID transactions. — SQL interface for introspection and reporting.
- sesm 3y agoSo the goal is to have a Redis-like API but not actually be an in-memory data store and reduce memory consumption this way? For example, for a project/service that started with Redis, but then priorities shifted and small memory footprint became more important than performance? Did I get it right?
- grobbyy 3y agoI can tell you my use case. I have a lot of systems which I'd like to use on a single computer AND at scale. That's sometimes even just for development work. A lot of these use a common API to a more complex distributed store, as well as to something simple like files on disk, in memory, or SQLite. I'm most cases, it's one user at a time, so performance doesn't matter, but simplicity does. It can also be for the project which has a 1 percent chance of going viral. Etc. But I find relatively few cases between truly small scale and large scale.
- sesm 3y agoLocal dev drop-in replacement for Redis seems like a really good usecase, thanks!