Hacker News Reader

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.

View on HN

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