Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Can You Replace API Management with Service Mesh?

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers.
Avatar for Solo.io Solo.io
September 10, 2020

Can You Replace API Management with Service Mesh?

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

Avatar for Solo.io

Solo.io

September 10, 2020
Tweet

More Decks by Solo.io

Other Decks in Programming

Transcript

  1. 4 | Copyright © 2020 As we move to services

    architectures, on cloud-native deployment platforms, we increase the complexity between our services.
  2. 6 | Copyright © 2020 API Management • Expose APIs

    • Enforce usage policy/quota • Throttle/spike arrest/rate limit • Security AuthN/AuthZ • Self service / developer portal • Lifecycle management • Analytics / monetization • Abstraction / transformation
  3. 7 | Copyright © 2020 Legacy API Management Challenges •

    Does not scale in cloud environments (static) • Typically implemented highly centralized • Bottleneck • Processes, no delegation • Automation • Built on legacy technology
  4. 11 | Copyright © 2020 Service mesh technologies provide the

    following: • Service discovery / Load balancing • Secure service-to-service communication • Traffic control / shaping / shifting • Policy / Intention based access control • Traffic metric collection • Service resilience • API / programmable interface
  5. 12 | Copyright © 2020 Can you replace API management

    with service mesh? What’s missing? • Enforce usage policy/quota • Throttle/spike arrest/rate limit • End user security challenges (Oauth2 flows/OIDC/LDAP) • Edge security (WAF) • Self service / developer portal • Lifecycle management • Analytics / monetization • Abstraction / transformation
  6. 17 | Copyright © 2020 Service mesh and API Gateway

    can use same proxy but for different purposes
  7. 18 | Copyright © 2020 Service mesh and API Gateway

    can use same proxy but for different purposes
  8. 19 | Copyright © 2020 Service mesh and API Gateway

    can use same proxy but for different purposes
  9. 20 | Copyright © 2020 What are the problems you’re

    trying to solve? https://twitter.com/christianposta
  10. 21 | Copyright © 2020 SERVICE A SERVICE C SERVICE

    B SERVICE D SERVICE E SERVICE F SERVICE G SERVICE H Federation Solo.io solves API connectivity & communication challenges Extension (Web Assembly) API Developer Portal
  11. 22 | Copyright © 2020 22 | Copyright © 2020

    What to watch for Upcoming improvements for which to keep an eye out
  12. 24 | Copyright © 2020 Web Assembly shaking up the

    data plane https://github.com/envoyproxy/envoy-wasm
  13. 25 | Copyright © 2020 Web Assembly shaking up cloud

    native infrastructure https://github.com/solo-io/wasm
  14. 27 | Copyright © 2020 More Resources • https://solo.io •

    https://slack.solo.io • https://gloo.solo.io • https://envoyproxy.io • https://istio.io • https://webassemblyhub.io • https://servicemeshhub.io • https://blog.christianposta.com