Postgres v Redis
Redis is faster than postgres when it comes to caching, there’s no doubt about it. It conveniently comes with a bunch of other useful functionality that one would expect from a cache, such as TTLs. It was also bottlenecked by the hardware, my service or a combination of both and could definitely show better numbers. Surely, we should all use Redis for our caching needs then, right? Well, I think I’ll still use postgres.
Some nice data and experimental setup for the comparison, jokingly discarded at the end for a broader point about software engineering tradeoffs. I largely agree with their conclusion too — maintaining two dependencies is more complicated, availability probabilities are multiplied, all for performance that the average enterprise service is unlikely to need.