Re:Ask HN: What are all the things that can go wrong during ...
by p410n3 on Friday March 13, 2020 @12:26PM
(#22568590)
This has happenend to steam!
https://forums.overclockers.co.uk/threads/do-not-login-to-an...
Re:Ask HN: What are all the things that can go wrong during ...
by anayar on Saturday March 14, 2020 @04:38PM
(#22578489)
But folks really cache auth related data? Isn’t that better handled purely through client <> server requests and handling caching for all UI or action based data?
Re:Ask HN: What are all the things that can go wrong during ...
by sethammons on Tuesday March 17, 2020 @09:56AM
(#22604871)
Not at scale. If our auth caching stops, our auth servers can get overloaded at peak times. Granted, horizontal scaling auth is a better first round choice, but caching gives you vertical scaling when you are hitting limits on your database. Another option is z-scaling, but that is really just a way to improve either of the previous two (have different pools of user databases).
If you add caching (esp. to your auth-chain), you need automated tests covering every access pattern. Concurrent access, cache timeouts, cache full, cache invalidation, etc.