In this article, senior architect Matt Bishop reviews the benefits and difficulties with a microservice architecture. While avoiding the “anti-patterns” and horror stories that are prevalent while sticking to the architecture qualities themselves.
Quick recap on considering microservices
In the first installment of the microservices series it laid out the definition of microservices from their qualities – loosely coupled, service-oriented and bounded contexts. These qualities enable a lot of things, but they also suffer some challenges.
A well-built microservices system delivers fundamental implementation independence. The services in the system are largely independent of each other and free to develop at their own pace. The system release changes often, without much coordination between the components. Over time the system acts more like an ecosystem where the whole business is supported by the coordination and ever-improving capabilities found therein.
An ecosystem like this has some observable characteristics: