Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

The Service Mesh: It's about Traffic

32 vues

Publié le

Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/2mcpD5B.

Oliver Gould talks about the Linkerd project, a service mesh hosted by the Cloud Native Computing Foundation, to give operators control over the traffic between their microservices. He shares the lessons they've learned helping dozens of organizations get to production with Linkerd and how they've applied these lessons to tackle complexity with Linkerd. Filmed at qconnewyork.com.

Oliver Gould is co-founder and CTO at Buoyant, Inc.

Publié dans : Technologie
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

The Service Mesh: It's about Traffic

  1. 1. The Service Mesh It’s About the Traffic Oliver Gould @olix0r
  2. 2. InfoQ.com: News & Community Site • 750,000 unique visitors/month • Published in 4 languages (English, Chinese, Japanese and Brazilian Portuguese) • Post content from our QCon conferences • News 15-20 / week • Articles 3-4 / week • Presentations (videos) 12-15 / week • Interviews 2-3 / week • Books 1 / month Watch the video with slide synchronization on InfoQ.com! https://www.infoq.com/presentations/ linkerd-cloud-native/
  3. 3. Presented at QCon New York www.qconnewyork.com Purpose of QCon - to empower software development by facilitating the spread of knowledge and innovation Strategy - practitioner-driven conference designed for YOU: influencers of change and innovation in your teams - speakers and topics driving the evolution and innovation - connecting and catalyzing the influencers and innovators Highlights - attended by more than 12,000 delegates since 2007 - held in 9 cities worldwide
  4. 4. Oliver Gould Photo Goes Here Linkerd Lead; Buoyant CTO @olix0r @olix0r @olix0r
  5. 5. Nov 9, 2016 QConSF
  6. 6. Agenda Why Does Linkerd Exist?�� The Trough of Service Mesh Disillusionment��♂ It’s All About the Traffic!��
  7. 7. 2/2016 1/2017 9/20182013
  8. 8. Control Plane ● Discovery ○ ZooKeeper ● Telemetry ○ Zipkin ○ Viz... Timelines Finagle (Library) Users Finagle (Library)
  9. 9. Service Mesh A C B
  10. 10. Service Mesh: Data Plane A C B Proxy Proxy Proxy
  11. 11. Service Mesh: Control Plane A C B Proxy Proxy Proxy Control Plane
  12. 12. An Abridged History of Linkerd ● 2016: Linkerd 0.1.0 ● Twitter-style Operability for Microservices ● Scala (JVM) + Finagle ● Extremely Powerful and Configurable
  13. 13. An Abridged History of Linkerd ● JVM sidecar too heavy for some users ● Difficult to configure ○ High barrier to entry ○ Many different configurations to support
  14. 14. How? 💪 Zero-config “just works”: If you have a functioning K8s app, drop in Linkerd without configuring anything. 💪 Fast and small: proxies should introduce the bare minimum perf and resource cost 💪 Understandable: no magic Data plane: linkerd2-proxy. Written in Rust. <10MB RSS, <1ms p99. (!!!!) Control plane: linkerd2. Written in Go. Includes small Prometheus (6 hour window), Grafana, etc.
  15. 15. Linkerd 2.x architecture
  16. 16. Strong Typing
  17. 17. No GC: RAII Resource Acquisition Is Initialization
  18. 18. What does Linkerd do? 👍 Visibility: Automatic golden metrics: success rates, latencies, throughput 👍 Reliability: Load balancing, retries, timeouts, circuit breaking, deadlines 👍 Security: Transparent mTLS, cert validation, policy Goal: Move visibility, reliability, and security primitives into the infrastructure layer, out of the application layer.
  19. 19. Linkerd: Observability ● Rich traffic metrics ○ Request rate, Success rate, latency ○ Across many dimensions ● Request inspection
  20. 20. Linkerd: Reliability ● Latency aware load balancing ● Retries ● Timeouts
  21. 21. Linkerd: Security ● Mutual, cryptographic identity ○ Bootstraps via Kubernetes ServiceAccounts ○ Transparent ○ On by default
  22. 22. An open source service mesh and CNCF project. 🔥 24+ months in production 🔥 3,000+ Slack channel members 🔥 10,000+ GitHub stars 🔥 100+ contributors 🔥 Near-weekly edge releases
  23. 23. The Trough of Service Mesh Disillusionment
  24. 24. Jeremykemp at English Wikipedia
  25. 25. What Can Go Wrong? 1. Can’t even get it working… 2. Trying to do too many things at once... 3. It’s always the mesh’s fault!
  26. 26. It’s All About the Traffic!
  27. 27. The Service Mesh Interface
  28. 28. Roadmap As of 2.3: 🗺 Telemetry, retries, timeouts, auto-inject, mTLS on by default. All zero config. 2.4 🗺 Traffic shifting (blue-green, canaries), install split. Mid term: 🗺 Policy, mesh expansion, distributed tracing, lots lots more.
  29. 29. F R O M Y O U R F R I E N D S A T Join our community! @linkerdgithub.com/linkerd slack.linkerd.io
  30. 30. Watch the video with slide synchronization on InfoQ.com! https://www.infoq.com/presentations/ linkerd-cloud-native/

×