5 ms·
In addition, you should worry about what happens to your app if a hardware error, network problem or natural disaster makes your machine unavailable.
by jupp0r 4y ago
In addition, you should worry about what happens to your app if a hardware error, network problem or natural disaster makes your machine unavailable.
- eddsh1994 4y agoSplit the DB from the app and replicate with a load balancer?
- jupp0r 4y agoNow you have "Production Twitter on three machines". Follow the rabbit and you end up with something like what Twitter looks like today.
- threeseed 4y agoThat database is going to need to be clustered as well for resiliency. Sounds like you already have quite a number of different containers already.
- eddsh1994 4y agoFour vms isn’t too bad to manage, I was the first dev at a startup that went prelaunch to acquisition from 2 App/DB servers in EC2 for a mobile app that hit #1 on both stores with a fairly high user tx rate and some ML stuff.
- pixl97 4y agoHeh, also praying that everything stays in the fast path. If a small portion of the workload uses a higher portion of machine resources then the moment an attacker figures it out they have a great way of DDOSing your service resources.