4 ms·
If your application is happy with an empty Redis, then why run Redis in the first place? What you say is good in theory, but doesn’t hold in practice. We use
by hinkley 2y ago
If your application is happy with an empty Redis, then why run Redis in the first place?
What you say is good in theory, but doesn’t hold in practice.
We use memcached instead of Redis. Cache different layers in different instances so one going down hurts but doesn’t kill. Or at least it didn’t when I was there. They’ve been trying to squeeze cluster sizes and I guarantee that’s no longer sufficient and multiple open circuit breakers happen if more than one cache goes tits up.
- ChocolateGod 2y agoCache and Sessions Both running in-memory speed up an application, but you can survive both being nuked (minus potentially logging everyone out).
- hinkley 2y agoNo. Cache protects your other services from peak traffic. Which often leads to wrong sizing of those services to reap efficiency gains. Autoscaling can’t necessarily keep up with that sort of problem. Remember how I mentioned circuit breakers? The only time we had trouble with memcached was when we set the max memory a little too high and it restarted due to lack of memory. Which of course likes to happen during high traffic. Not fixing those would have resulted in a metastable situation.
- marklubi 2y agoPub/Sub is a huge use case for me