News for hackers. Stuff that matters.

A comment on The GitHub Availability Report. Parent comment

Re:The GitHub Availability Report by aneutron on Thursday July 16, 2020 @02:20AM (#23856340)
I might be wrong, but you probably didn't handle as much traffic as Github does. Bugs and outages probability is a asymptotic to normalized traffic. At least intuitively.
[ Parent | on HN ]
Re:The GitHub Availability Report by KingOfCoders on Thursday July 16, 2020 @03:24AM (#23856662)
No we didn't luckily but we also didn't have that much money. Biggest problem was 50k+ people trying to reserve a limited amount of stuff at the same time and 5k+ logins/second (at first we made the mistake to write last_login to MySQL ;-)
[ Parent | on HN ]
Re:The GitHub Availability Report by KingOfCoders on Thursday July 16, 2020 @07:49AM (#23858005)
We changed to a write behind setup (e.g. with Redis PubSub or any other queue). I think everyone with some experience will use async write behind and not sync writes during a request as we did.
[ Parent | on HN ]
Re:The GitHub Availability Report by d0100 on Thursday July 16, 2020 @07:43AM (#23857956)
How did you go about saving login/device data? We are going to do this soon in our app and I'm looking for good use cases and solutions
[ Parent | on HN ]