Fireside chat - Monoliths, Microservices & Modernization – Practical Strategies
summary
A bank moves from a Java monolith to a platform running 50+ microservices with containerized apps, streaming tech and CI/CD that supports multiple deployments per day. The migration uses strangle the monolith by carving single backend capabilities, applies domain‑driven design for service boundaries, and keeps an open source stack to avoid vendor lock‑in. Teams go adaptive (13 cross‑functional product teams), favor mature tools over experiments, and avoid a risky big‑bang release.
AI-written summary · about
chapters (27)
- 0:00Intro
- 2:04What have you done before
- 3:02Where are you now
- 4:55Biggest challenges
- 6:15What worked
- 7:42Challenges
- 8:44Legacy
- 9:52Best practices
- 11:16Why open source
- 12:27Switching to open source
- 13:34Being an expert
- 14:52Being proactive
- 16:12Seniors juniors react differently
- 17:13Digital transformation
- 18:00Making it easier for hiring
- 18:51Business mentality
- 19:24Adaptive teams
- 20:43Challenges faced
- 21:19Engineering in the bank
- 22:51Regulations
- 24:24Experimenting
- 25:29Regulation
- 26:03Roadmap
- 26:48Developers
- 27:24Big bang
- 28:44Drunk leg
- 29:29Monolith to Microservice
related talks
42mFrom Monolith to Microservices: The Evolution of a Banking Platform
01h 03mFrom Monolith to Microservices: Story and Practice
42mQ&A - Monolith to Microservices
32mSplitting the monolith
38mFrom Monolith to Microservices
48mMicroMonolith
39mConsidering Migrating a Monolith to Microservices?
31mMonolith to Microservices: A Guide to Seamless Transitions