Microservice.add(observability) != Microservice.add(monitoring)

Written by kayalvizhi | Published 2020/06/22
Tech Story Tags: observability | microservices | resiliency | monitoring | services | inter-service-communication | logging | hackernoon-top-story

TLDR A single transaction can flow through many independently deployed microservices, or pods, and discovering where performance bottlenecks have occurred provides valuable information. Microservices ain’t easy, but it’s necessary. Distributed systems are pathologically unpredictable. An obvious area where it adds complexity is communications between services. A primary microservices challenge is trying to understand how individual pieces of the overall system are interacting. So, in short, observability is not a panacea, but is the ability of the data collected from these data collected.via the TL;DR App

no story

Written by kayalvizhi | Principal Software Architect, Microservices & Cloud Computing enthusiast, Hands-on Java Developer
Published by HackerNoon on 2020/06/22