dev@cloudburo

There is a quite a hype in the Mircoservice architecture style, so it’s good that one of the well-known architecture heavy-weight is listing  some important competencies necessary to successfully work with this style. 

Martin Fowler outlines in this article the trade-offs and operational consequences of a micro service architecture :

In particular with microservices there are serious consequences for operations, who now have to handle an ecosystem of small services rather than a single, well-defined monolith. Consequently if you don’t have certain baseline competencies, you shouldn’t consider using the microservice style.

will be key. 

With this kind of setup in place, you’re ready for a first system using a handful of microservices. Deploy this system and use it in production, expect to learn a lot about keeping it healthy and ensuring the devops collaboration is working well. Give yourself time to do this, learn from it, and grow more capability before you ramp up your number of services.