Microservices need to be coupled with containerization, iac, ops, container orchestration, data management, deployment, service orientation, eda, and git/vc development principles (not finite). "Unless" the team identifies the right tools for each job, the task will always have "increased development complexity" and "organizational overhead". Navigating through the ocean of choices is what an architect should do; and pick the leanest tools to carry on the hipbelt.
It is "hard" for development teams who have built monoliths to "unlearn" and now "think" microservices, events, streams; i.e. after the decision has been "voted in".
Developer experiences are critcal, and when the developer is abstracted away from the underlying complexity of iac, and other base APIs/fns - writing BL with MS is then simpler.
The linked Shopify articles quotes "If no architecture is enforced, the result will likely be a monolith." :) Stunning!
MS is not a toy - but coupled with the learnings involved is super fun!
I almost agree with every statement you made. To be clear, I’m not anti-Microservices but rather wish to ensure that individuals are aware of the costs involved and have knowledge of alternative options. There is always a trade-off, but I think that’s the beauty of the software development world.
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.
Nicely put - but can't agree with the article.
Microservices need to be coupled with containerization, iac, ops, container orchestration, data management, deployment, service orientation, eda, and git/vc development principles (not finite). "Unless" the team identifies the right tools for each job, the task will always have "increased development complexity" and "organizational overhead". Navigating through the ocean of choices is what an architect should do; and pick the leanest tools to carry on the hipbelt.
It is "hard" for development teams who have built monoliths to "unlearn" and now "think" microservices, events, streams; i.e. after the decision has been "voted in".
Developer experiences are critcal, and when the developer is abstracted away from the underlying complexity of iac, and other base APIs/fns - writing BL with MS is then simpler.
The linked Shopify articles quotes "If no architecture is enforced, the result will likely be a monolith." :) Stunning!
MS is not a toy - but coupled with the learnings involved is super fun!
I almost agree with every statement you made. To be clear, I’m not anti-Microservices but rather wish to ensure that individuals are aware of the costs involved and have knowledge of alternative options. There is always a trade-off, but I think that’s the beauty of the software development world.