You can observe three key characteristics of microservices in figure 1.1:
¡ Each microservice is responsible for a single capability. This might be business related or represent a shared technical capability, such as integration with a third party (for example, the stock exchange).
¡ A microservice owns its data store, if it has one. This reduces coupling between services because other services can only access data they don’t own through the interface that a service provides.
¡ Microservices themselves, not the messaging mechanism that connects them nor another piece of software, are responsible for choreography and collaboration —the sequencing of messages and actions to perform some useful activity
If an existing application has N services; and each service connects few down stream applications (using SOAP web services) and use that data for business logic;
Is it possible to re-design (implement) existing application services as micro services; my doubt is until down stream systems are monolithic, can we assume new implementation as micro services.
or does this means, if an application which is dependent on few down stream applications, can not be true micro service architecture until dependent applications have monolithic charc.
thanks & regards.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop