3 ms·
I don't understand why people treat microservices or monoliths as either or. If I find my various projects using the same functionality over and over, then I'll
by yawnxyz 5y ago
I don't understand why people treat microservices or monoliths as either or. If I find my various projects using the same functionality over and over, then I'll split that off as a microservice to serve my monolith projects of various sizes.
It's like functions: don't turn code into a function until you need it in three different places.
- galovics 5y agoI agree but the trend still seems to prefer one or the other and that's why it's so important to talk about the potential downsides instead of closing our eyes and saying everything is gonna be better if we do microservices.
- foobarian 5y agoMaybe it's just the activation energy. Until you have the setup for making a microservice, you're kinda limited to a monolith. Once you pay the setup cost though, making incrementally more services is trivial so you end up on the other end of the spectrum.
- marcus_holmes 5y agoOr you could have it as a module/library that you import into all your monoliths, and save the communication overhead. But then, I'm firmly in the old-skool "don't split the monolith until you absolutely have to" camp.