Using an Observability Platform to Understand Multi-Layered Architectures

Easy-to-understand monoliths are giving way to distributed systems: microservices, serverless, meshes, proxies, and every possible combination.

These systems offer developers the freedom to build new features and technology faster, as they are no longer beholden to the elaborate release processes associated with monolithic architecture.

But, like all good things, there is a price: Distributed systems are inherently difficult to operate and maintain.

DBTA recently held a webcast with Austin Parker, principal developer advocate, LightStep, who discussed how observability can help developers understand multi-layered architectures.

Traditional tools weren’t built for deep systems, Parker said. Users may be scrolling through dashboards that don’t reveal root cause or spent time sifting through logs for that [expensive] needle in a haystack.

Organizations need visibility across services and dependencies, according to Parker.

The right observability solution should:

  • Easily be able to see and understand your highly distributed environment
  • Immediately pinpoint performance regression
  • Enable developers to ship with confidence
  • Enable easy sharing of information
  • Keep context
  • Won’t miss an insight

Lightstep offers an observability platform with context. The platform includes:

  • Automatic deployment and regression detection
  • System and service diagrams
  • Real-time and historical root cause analysis
  • Correlations
  • Custom alerting
  • Easy Setup with no vendor lock-in
  • No cardinality limitations, really

An archived on-demand replay of this webinar is available here.