In the pursuit of faster deployment, we’ve broken up monoliths into microservices. These loosely-coupled, independently deployable components are built and managed by individual teams that can more quickly respond to their customers’ needs. However, one microservice is not a complete system. While one team may benefit from the reduced cognitive load that comes with only being responsible for their services, who is in charge of the big picture?
The companies that are successfully operating distributed systems use tools and techniques that address operational concerns of the individual microservices as well as for the whole system. This eMag features content from InfoQ articles and presentations from the Operating Microservices track of QCon Plus.