Re:The GitHub Availability Report
by mattip on Thursday July 16, 2020 @01:43AM
(#23856157)
If you are running an app that is basically a UI layer over a database, where would you expect significant failures to occur? The users are already debugging possible problems with git locally by simply using it, so UI-database interactions are where all the action happens on products like github.
[ Parent
| on HN ]
Re:The GitHub Availability Report
by KingOfCoders on Thursday July 16, 2020 @02:02AM
(#23856249)
When I was CTO in some companies we had very different problems, with DBs being only one of them (and thankfully not four hour long outages in two months).
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.
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 ;-)
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.