Hacker News Reader

I simply explained the efficiency difference of the two setups.

You're storing and checking a smaller subset when doing stateless + invalidation cache.

Whether or not you need that memory optimization is up to you and your machines.

Personally it's about the same effort to implement and I prefer stateless + simple redis cache for invalidations.

Well, on the other hand, you will have to distribute that revocation list somehow, what does add some complexity to your code.

If you are already distributing lists around your application servers (that impacts the format and top performance of the redis cache), then yes, it's quite simple.

Redis is pretty easy to distribute out of the box.

And most likely you'll want a simple k/v distributed cache for other things so it's no extra work.

But then you can just put your session data in Redis. You're eating the latency to Redis either way.

Reply on news.ycombinator.com