A commonly asked question is “can I replace the edge/API gateway or API management solution with a service mesh?” While the service mesh solves communication challenges between services in a cluster (east/west traffic), there still exists the need to manage the traffic entering and exiting a cluster (north/south traffic), and while complimentary, they are different traffic patterns. Additionally, not all applications are able to run in Kubernetes and service mesh or even as a container.
This Presentation Covers:
* Evolving traffic patterns from the edge/ingress to service mesh
* How the traffic patterns differ and areas for integration
* Envoy as the underlying proxy technology for the modern application network
* Key capabilities of Envoy based networks
* How to incrementally adopt and operationalize across multiple clusters
Watch the video https://youtu.be/fwRBB5usYHQ
Learn More https://www.solo.io
Join the community https://slack.solo.io
Request a demo https://lp.solo.io/lp-request-a-demo-overview