Slicing 'Big Elephant' systems into micro-services
summary
A team splits a monolithic banking system by building three microservices: extractor (called pepper), REST API, and UI service, using Spring Boot, OpenShift and Netflix OSS and wiring delivery pipelines to push into production. A quick proof-of-concept runs in three weeks, wins client buy-in, secures normal innovation budget and delivers a minimal viable product to production within about four weeks, overcoming firewall, DB and regulatory coordination. The result is working features in production and other teams adopting the same platform.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 2:43Life in a big bank system
- 7:31Challenges of legacy systems
- 10:01Deciding to try microservices
- 15:26Building the first microservices
- 18:40Demo and client reaction
- 20:06Moving to production
- 23:03Results and spreading adoption
- 25:31Choosing to stay alive as a developer
related talks
42mFrom Monolith to Microservices: The Evolution of a Banking Platform
18mMicroservices Out In the Wild
45mDesigning, building, testing and deploying microservices
43mBreak Up the Monolith: Testing Microservices
29mMoving from A and B to ~150 microservices, the journey and learnings
23mOn the road from Monolith to Micro
57mSplitting Monolith Application to Microservices
51mMicroservices and Microfrontends: Scaling, Learning, Growing