The World after Microservice Migration w/ Service Mesh & Contract Testing
summary
Refactors a Scala monolith into microservices, then shows the concrete infra used to keep things working: linkerd v1 on AWS ECS with Consul and registrate for dynamic routing, later moving to Kubernetes and noting Envoy/Istio trends; benchmarks show p99 adds ~5–6 ms up to 20k rps. For contracts it uses Pact and a Pact Broker in CI to publish and verify consumer-driven contracts, records legacy traffic with WireMock, and reports a six-month migration with no user-facing breakage.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:22Agenda
- 1:01The problem
- 4:34Service Mesh
- 6:51Deploying Service Mesh
- 8:50Identification
- 10:41Binding
- 12:38Resolution
- 14:07Performance Penalty
- 14:51Demo
- 25:35ConsumerDriven Contract Testing
- 26:10Contract Testing Example
- 36:46Pact Broker
related talks
39mGrow with Less Pains - Meshing From Monolith to Microservices
35mNavigating the Service Mesh Ecosystem
24mFrom Monolith to Microservices: A Journey into the Mesh
28mThe journey from monolith to microservices
31mMonolith to Microservices: A Guide to Seamless Transitions
51mHow to get a grip on your microservices system using a service mesh
43mEnhancing Backend Microservices Ecosystem with Contract Testing
24mPatterns of Evolution from Monolith to Microservices