So you think you can mesh? Scaling ING's service mesh
summary
ING scales a service mesh from 1 to ~10,000 running instances over 8 years, servicing 37 million customers and ~2,000 microservices and already handling about 180 million requests; core pieces are a API Marketplace that issues JWT subscriptions and endpoint-level discovery, a control plane feeding a data plane with observability and client-side load balancing, automated certificate issuance for Mutual TLS, a Spring Boot library plus an in-house sidecar, an insides dump for runtime telemetry, and a regression suite that validates behavior during sidecar replacement.
AI-written summary · about
chapters (12)
- 0:00Introduction to service mesh
- 1:10What is a service mesh
- 8:34Service mesh at ING
- 10:00The three planes explained
- 11:02Governance plane and API Marketplace
- 17:35Service Discovery in practice
- 20:08Security in the data plane
- 23:00Resiliency and observability
- 24:51Balancing abstraction and control
- 33:47Evolving the service mesh
- 37:26Service mesh as abstraction
- 39:58Q&A session
related talks
29mSo you think you can mesh? Scaling ING's service mesh
17mDesigning a Service Mesh for Global Scale At SAP
39mGrow with Less Pains - Meshing From Monolith to Microservices
11mWelcome & Opening Remarks
39mAPI Gateway to Service Mesh: Navigating a Changing Landscape
20mThe Crazy Service Mesh Ecosystem
40mReimagining Application Networking and Security
26mService Mesh Journey - Building Security and Reliability One Si...
