Monday, March 14, 2016
Thursday, March 3, 2016
Microservices Ending up as a Distributed Monolith
If a service cannot interact within a system unless all these libraries are available, then Christensen calls this a distributed monolith. Essentially all you have done is spread a monolith over the network paying all the cost of a distributed system but losing a lot of the benefits of the microservices architecture. Some of the benefits lost include the characteristic of polyglot, meaning that you loose the possibility of services adopting the best technologies to solve the specific problem, and organizational and technical decoupling, allowing for a team to evolve technically without first having to convince a central authority.
The alternative for Christensen is contracts and protocols, services should hide all their implementation details only exposing data contracts and network protocols.
Subscribe to:
Posts (Atom)