Redis excels at sub-millisecond operations - thats what you get when you use an in-memory data store. If you are conflating Postgres and Redis then it's doubt y

Redis excels at sub-millisecond operations - thats what you get when you use an in-memory data store. If you are conflating Postgres and Redis then it's doubt you really actually needed either. Strong persistence or consistency isn't something that is very popular in Redis (or at least I haven't seen it done). In most cases you are right - if you are willing to trade latency for persistence or consistency there are other tools available. I wouldn't read that much into tidis - it seems like a hobby project for now. Another interesting redis project is pedis (https://github.com/fastio/pedis https://github.com/fastio/pedis). It takes advantage of multiple cores by, at a high level, sharding the keyspace per core.