Re:How Instagram scaled to 14 million users with only 3 engi...
by ahoka on Saturday September 16, 2023 @06:09AM
(#37533481)
Bad input crashes app, monolith fails over, other instance crashes. Full outage.
Assuming proper vertical separation, this risk can be reduced by microservices.
[ Parent
| on HN ]
Re:How Instagram scaled to 14 million users with only 3 engi...
by elktown on Saturday September 16, 2023 @06:33AM
(#37533604)
It might just as well be increased by microservices due to fragile dependency chains and just different people working async and what not.
Re:How Instagram scaled to 14 million users with only 3 engi...
by ahoka on Monday September 18, 2023 @02:35AM
(#37552955)
Maybe read my comment again.
Re:How Instagram scaled to 14 million users with only 3 engi...
by elktown on Monday September 18, 2023 @07:36AM
(#37554850)
Care to enlighten me? Your comment is essentially "assuming the best case scenario for X and worst case scenario for Y, X can reduce the risk". Well, you don't say.
Re:How Instagram scaled to 14 million users with only 3 engi...
by BoorishBears on Saturday September 16, 2023 @01:02PM
(#37536534)
This is not what microservices solve.
There'll always be critical microservices that keep your app running. It doesn't matter if all your other services are running if the one serving up core functionality goes down.
If your engineering rigor is so poor that you can't get reliable failovers with a monolith, god help you keeping microservices running.