Tweet
Tweet

Slide 1

Slide 1 text

Can You Replace API Management with a Service Mesh Christian Posta Field CTO – Solo.io

Slide 2

Slide 2 text

2 | Copyright © 2020 Our customers’ challenges

Slide 3

Slide 3 text

3 | Copyright © 2020 Inspiration https://solo.io/blog

Slide 4

Slide 4 text

4 | Copyright © 2020 As we move to services architectures, on cloud-native deployment platforms, we increase the complexity between our services.

Slide 5

Slide 5 text

5 | Copyright © 2020 How we typically like to solve this problem:

Slide 6

Slide 6 text

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

Slide 7

Slide 7 text

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

Slide 8

Slide 8 text

8 | Copyright © 2020 Enter the service mesh!

Slide 9

Slide 9 text

9 | Copyright © 2020 Service proxy lives with application instance

Slide 10

Slide 10 text

10 | Copyright © 2020 Service proxy lives with application instance

Slide 11

Slide 11 text

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

Slide 12

Slide 12 text

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

Slide 13

Slide 13 text

13 | Copyright © 2020 How do we get there? http://envoyproxy.io

Slide 14

Slide 14 text

14 | Copyright © 2020 Versatility of Envoy: Edge proxy

Slide 15

Slide 15 text

15 | Copyright © 2020 Versatility of Envoy: Middle proxy

Slide 16

Slide 16 text

16 | Copyright © 2020 Versatility of Envoy: Service proxy

Slide 17

Slide 17 text

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

Slide 18

Slide 18 text

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

Slide 19

Slide 19 text

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

Slide 20

Slide 20 text

20 | Copyright © 2020 What are the problems you’re trying to solve? https://twitter.com/christianposta

Slide 21

Slide 21 text

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

Slide 22

Slide 22 text

22 | Copyright © 2020 22 | Copyright © 2020 What to watch for Upcoming improvements for which to keep an eye out

Slide 23

Slide 23 text

23 | Copyright © 2020 Web Assembly shaking up the data plane

Slide 24

Slide 24 text

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

Slide 25

Slide 25 text

25 | Copyright © 2020 Web Assembly shaking up cloud native infrastructure https://github.com/solo-io/wasm

Slide 26

Slide 26 text

26 | Copyright © 2020 @christianposta @christianposta christian@solo.io https://blog.christianposta.com https://slideshare.net/ceposta

Slide 27

Slide 27 text

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