4 ms·

I think your argument makes sense but the example you gave is far too extreme. Also, isn't splitting things into small services instead of large beasts full of

• lexicality 6y ago
  > I think your argument makes sense but the example you gave is far too extreme. It was a bit of an exaggeration yes, but it made my point about neglecting rarer failure cases very succinctly. > Also, isn't splitting things into small services instead of large beasts full of hidden behavior the basis of the argument in favor of microservices? With microservices your goal should always be simplicity rather than size. Simple code is often small, but small code is not always simple. In fact, 3 well built microservices will usually have more lines of code between them than a single monolith that does the same job would as they have to have all the boiler plate for talking to each other and accepting RPC etc. (Also converting a large system that's hard to reason about into microservices generally results in a large distributed system that's hard to reason about - system design is hard!)