3 ms·
The offered solution to use a centeral memcache/Redis server is exactly why we moved to JWT. First memcache and then Redis sessions were a continuous centerali
by donatj 8y ago
The offered solution to use a centeral memcache/Redis server is exactly why we moved to JWT.
First memcache and then Redis sessions were a continuous centeralized source of failure we could remove, and honestly didn’t scale very cleanly approaching millions of users.
Removing moving parts from our stack was a major win.
That’s not to say JWT is without thorns, but overall it’s better than a centeralized point of failure.
- gm-conspiracy 8y agoI am curious about your experience with Redis and millions of users...what were the issues you experienced?
- donatj 8y agoIn particular we weren't storing a ton per session, but were having to spin up more and more instances or suffer port exhaustion. We go from about 25,000 request a second during the day to 200 at night, and there was no good way we could find to autoscale it. We scripted the build up process based on time and sometimes it wasn't meeting demand. It was taking a lot of devops time. I'd had an experimental fork of our application using JWT floating around for a while and my manager made it a priority. It's never needed any maintaince and had been a real improvement for us.