Routing Your Microservices Architecture
summary
traffic is a dynamic edge router rewritten as traffic v2 (27k stars, ~450 contributors, ~100k instances) that adds TCP routing, chained middlewares, canary/mirroring and built‑in Let’s Encrypt support. Demo deploys to a DigitalOcean Kubernetes cluster using an ingressroute CRD, shows entrypoint→router→service flow, config hot‑reload, a 3:1 canary split, and successful TLS issuance. A lightweight service mesh runs per node (no sidecars) via SMI and Helm and works in the demo.
AI-written summary · about
chapters (14)
- 0:00Start
- 1:03Introduction
- 3:23The Layered Monolith
- 4:03Promise of Micro Services
- 6:48Facts about the Traffic Project
- 8:50Edge Router
- 9:40Entry Point
- 10:06Routers
- 12:52Differentiation in Config
- 16:34Ingress Route
- 17:56Demo
- 22:31Dashboard
- 25:22Cannery
- 27:57Middleware Redirect
related talks
21mServiceRouter: Hyperscale Service Mesh
33mMircoservices the right way: an introduction to Istio
58mService Mesh and Sidecars with Istio and Envoy
52mEmpower Your Microservices with Istio Service Mesh
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
27mService Mess to Service Mesh
56mHow to get a grip on your microservices system using a service-mesh
50mDeveloping Microservices with Istio