5 ms·
This frankly adds nothing new to the conversation. And if you find scaling microservices harder than a giant stateful monolith well then clearly you've done so
by threeseed 9y ago
This frankly adds nothing new to the conversation.
And if you find scaling microservices harder than a giant stateful monolith well then clearly you've done something wrong.
Likewise local development should be far easier if you define your APIs and contract boundaries properly.
- godzillabrennus 9y agoThe author did a better job convincing me of the benefit of micro services than they did trying to outline the cons. I'm now more of a proponent for them than I was when I started reading.
- viraptor 9y agoAdditionally, if you're actually having issues with scaling microservices or using them reliably for some reason, it's usually pretty easy to integrate two of them into a bigger piece. Virtually always easier than extracting a new microservice from an existing monolith.
- sbov 9y ago> And if you find scaling microservices harder than a giant stateful monolith well then clearly you've done something wrong. Monoliths don't have to be stateful anymore than a microservice does. Stop arguing against strawmen. This is why this topic is maddening.
- sundvor 9y agoI somewhat recently worked on a huge monolith where certain parts were "off limits"; I was told to the effect of "noone changes those classes, we don't really understand them". That business is not going too well now. I searched the article for "domain" and "bounded contexts", found nothing. Article is not without merit, however; Sam Newman in his book [1] cautions about going too aggressive, i.e. splitting down into too many microservices before the domain is fully understood. On the other hand, having systems cross obvious domains is a definite warning sign (of disaster). So the motto might be, use them, but in moderation (as with a lot of things). 1) https://smile.amazon.com/Building-Microservices-Designing-Fine-Grained-Systems/dp/1491950358 https://smile.amazon.com/Building-Microservices-Designing-Fi...
- ex_amazon_sde 9y agoAmazon has been a precursor of SOA. There's no "Micro" in SOA, for a reason.