I would like to add two points, which is are not mentioned - at least not explicitely:
a) Developer skillset
It requires different skillsets to run one or the other. If you have a team with sharp skills developing microservices, it would be reasonable to think of doing microservices for upcoming projects.
b) Although monoliths aren't always simple, agreed. But are in terms of complexity easy to reason about. In the world of microservices a simple function call turns into a distributed systems problem. With a bit of humor:
You could - of course - do microservices with a team, knowing only one language ;)
Actually it happens most of the time :) It's advantage rarely used, only when it really could solve a big problem.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for this great writeup!
I would like to add two points, which is are not mentioned - at least not explicitely:
a) Developer skillset
It requires different skillsets to run one or the other. If you have a team with sharp skills developing microservices, it would be reasonable to think of doing microservices for upcoming projects.
b) Although monoliths aren't always simple, agreed. But are in terms of complexity easy to reason about. In the world of microservices a simple function call turns into a distributed systems problem. With a bit of humor:
twitter.com/tenderlove/status/1027...
But anyways a good thread.
P.S:
You could - of course - do microservices with a team, knowing only one language ;)