Platform memory is locked to one model and one company. Stash brings the same capability to any agent — local, cloud, or custom. MCP server, 28 tools, background consolidation, Apache 2.0.
I started redix with redis protocol to make use of redis ecosystem out there. There is also a plan to make HA a native feature in redix with no external requirements, so I can keep redix a standalone DB server.
1- Multi: yes, I'm planning to support it in the next releases.
2- Consistency: Yep, also there will be test cases soon.
3- Performance: at first, nothing will be faster than RAM, so don't expect that an on-disk store is faster than an in-memory store, but that doesn't mean that on-disk stores are very slow, I selected two storage engines called bolt and badger, badger is the default because it follows RocksDB design and rocksdb. for redix server compared to redis server, redix doesn't use an eventloop, but each connection runs in its own light-weight thread, so there no possibilities that you run a command and block the server itself, another note is: the underlying implementation of internal datatypes makes redix faster in some cases especially when you try to load large datasets, you will notice that redix has very low response time than redis, that means, in a highly loaded environment you find redix performance better than redis especially with the coming version because redix will lower the memory usage more and more.
Every day I improve it more and more, and thanks for the issues creator on the repo, they're helping me too in organizing my thoughts.
So, mysql is a frontend to InnoDB?
Cockroach is a frontend to RocksDB?
Note:
Redix has a pluggable storage engine, the current engine is "badgerdb", the next is "bolt" and it is already integrated and I'll release it soon.