3 ms·
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 po
by mattip 6y ago
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.
- KingOfCoders 6y agoWhen 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).
- aneutron 6y agoI 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.
- KingOfCoders 6y agoNo 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 ;-)
- d0100 6y agoHow 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
- KingOfCoders 6y agoWe 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.