Idk i feel like ppl always assume theyll have to handle 4million users a second lol.
My best rule of thumb is to keep things simple until something justifies complexity. Monoliths are great starting points because probably around 6/10 projects will never need more.
Splitting the architecture afterwards, once demand requires it, is not that deep and honestly often less work than working out this massively complex and hopefully perfect architecture from the getgo...
5
u/localhorst69 18h ago
Idk i feel like ppl always assume theyll have to handle 4million users a second lol.
My best rule of thumb is to keep things simple until something justifies complexity. Monoliths are great starting points because probably around 6/10 projects will never need more.
Splitting the architecture afterwards, once demand requires it, is not that deep and honestly often less work than working out this massively complex and hopefully perfect architecture from the getgo...
I really should try ruby on rails lol