~/talk

WTF Do We Need a Service Mesh?

Talkat Cloud Native & OSS Day Tel Aviv 2019 · on Tuesday, 2019-12-03· [microservices]
slides:none on file

Service mesh is a sidecar+control-plane pattern that makes service-to-service networking manageable by adding proxies (Envoy, Linkerd2 proxy) and control APIs (SMI). It enables traffic split, progressive delivery (blue/green, canary) and observability (service-level percentiles, success/failure counts); Istio drops from ~50 to ~20 components since 1.0, is available as a managed GKE add-on, and suffers mixer hot spots addressed by mixer v2/WASM. Benchmarks claim Linkerd (Rust proxy) outperforms Istio; alternatives include Consul, Traefik/Kuma approaches and Network Service Mesh for L2/L3 use cases.

AI-written summary · about

  1. 0:00Start
  2. 9:03QUESTIONS
  3. 12:35MESH VS GATEWAY
  4. 14:27SMI - THE SERVICE MESH INTERFACE
  5. 26:08LINKERD 2.0
  6. 27:54CONSUL CONNECT
  7. 31:13KUMA (KONG MESH)
  8. 32:21NSX - NETWORK SERVICE MESH
  9. 34:08ECOSYSTEM!
  10. 37:10BENCHMARKS
  11. 40:43GET INTO THE MESH
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.