code base • L3/L4 filter architecture • HTTP L7 filter architecture • HTTP/2 first • Service discovery and active/passive health checking • Advanced load balancing • Best in class observability (stats, logging, and tracing) • Edge proxy
that Envoy provides. • Having all SoA traffic transit through Envoy gives us a single place where we can: ◦ Produce consistent statistics for every hop ◦ Create and propagate a stable request ID / tracing context ◦ Consistent logging ◦ Distributed tracing
data sources that are not linked. • Cognitive load of different data sources make issue investigation with traditional stats, logging, and tracing is VERY high • Service mesh yields an observability base that allows us to do incredible things by default. How can we reimagine observability and operations in the age of the service mesh?
like Envoy provides unified APIs for control as well as consistent observability output. • Allows us to build more feature-rich full service mesh solutions such as Istio. • When we assume the existence of the service mesh, we can focus on an incredible UI/UX instead of constantly trying to keep every application up to date. • Assume that service mesh is the future… All data is available. • We need to start building the UI/UX/ML of the future for distributed system command control. Need to start now!