Re:Kernighan and Pike were right: Do one thing, and do it well
by dgb23 on Saturday August 19, 2023 @08:44AM
(#37188204)
None of those things require you to introduce network calls.
Re:Kernighan and Pike were right: Do one thing, and do it well
by renegade-otter on Saturday August 19, 2023 @08:46AM
(#37188221)
And what if a certain permutation of these hundreds of services goes down or slows down? What if one service starts generating tons of data and floods another service? Do you have backpressure figured out? Distributed systems introduce a whole new level of complexity and edge cases, but most companies never even hit the scale at which it matters. It's just a pointless, wasteful exercise in "how they do it over at Google".
Re:Kernighan and Pike were right: Do one thing, and do it well
by marcosdumay on Saturday August 19, 2023 @09:17AM
(#37188461)
Nothing that can't be solved with more code and more splitting! That will make things simpler! The more problems your code causes, the more code, the more solutions!
(Well, ok, I'm having a hard time solving the first one with more code, but did hear this claim applied to it more than once, so I'm keeping it general.)
There is a huge amount of people that sees nothing wrong with my rationale up there. I don't get it either.
No, of course not. We divide a single machine in an uncountable number of virtual ones; write some code to make sure they don't talk to each other; write some code to make them able to talk to each other; write some code make more or fewer divisions on the run, automatically; and write some code so we can set them up automatically too every time we get a new split.
That's how you use software scalability and create a simple, predictable ops environment.