This is me speaking from 2+ years of experience building greenfield products adopting "industry standard" practices. Doing that was a mistake that we keep repeating.
The industry standard should not be treated as a given. If your engineering team doesn't have the technical discipline to explain why you need the industry standard, then you shouldn't use the industry standard.
If you have to ask why you're doing microservices, chances are you do not need microservices.
And I return to the point about the domain model not being treated as an architectural blueprint:
The network is the most fragile part of your architecture. If you take it for granted, your systems will become failure-prone messes.
Don't do microservices, until you truly need it.
The efforts done to make microservices architecture "easy" were themselves incredibly expensive. So why did anyone invest into it?
Because the companies that went to it had a practical need to break things down into smaller components, and it was cheaper to invest in the research for e.g. gRPC or other technologies that make the implementation of microservices more robust than to continue scaling vertically.
The problem with implementing every DDD service as a "microservice" is the amount of complexity you add to the intercommunication of those services. No, HTTP REST is not free. It is in fact very expensive to maintain.
Strangler Pattern exists to address monoliths that exist in practice, not to avoid monoliths that exist in theory.
I'm also, unironically, Pebble the Cockatoo when I get off of work and screaming about shit
has poor taste in video games
yes you can follow request
please ask in a DM for discord/other app to contact me directly. DMs here are not a great direct medium
avatar by @pinnapop@twitter.com