Microservices Out In the Wild
summary
Fitch Solutions migrates a monolithic web UI into vertically aligned full‑stack microservices, running 150 microservices in Kubernetes and serving micro UIs that map to their own backend services. State changes are published to event-sourced Kafka topics so each service replays events into a local cache database; Istio’s service mesh routes traffic to parallel versions enabling feature gating and phased rollouts. SonarQube and automated unit/integration/security checks in CI block bad builds—demo shows Bamboo failing on a bad file then succeeding after a fix.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:56Problem statement
- 2:31Previous situation
- 3:41Kubernetes
- 5:06SONARQube
- 6:14Kafka
- 7:35Target situation: "event sourced architecture"
- 8:35Why service mesh?
- 12:24Continuous delivery
- 14:17New situation
- 15:45Demo
related talks
36mMicroservices Lessons Learned
51mMicroservices and Microfrontends: Scaling, Learning, Growing
35mSeven years with microservices: a critical review
57mSplitting Monolith Application to Microservices
52mMicroservices: A Utopian Mystery
44mMicroservices - How to create problems by solving problems?
44mRoute to microservices the epic voyage of a fintech leader
43mGo micro with Microservices