Transforming a monolith to an API platform
summary
Company with ~200–250 engineers moves a 2001 Java monolith toward an API platform by extracting hot endpoints, deploying an API gateway and containerizing. They run Spring Boot, documented via OpenAPI, replaced Zuul with Spring Cloud Gateway in prototypes, use Kafka for queues plus RPC for internal calls, and package with Docker/Helm on AWS EKS. Repo stats: top‑3 size, ~100 commits/day, ~500 active branches. Logging via ELK with 10‑year retention, CI uses Jenkins/Artifactory; EKS reduces build VM costs. Challenges: cross‑service comms, polyglot ops, and tool churn (Zipkin/Jaeger/OpenTelemetry).
AI-written summary · about
chapters (18)
- 0:00Start
- 4:16From Monolith to an API Platform
- 6:44be Domain-driven decisions for designing the Products
- 9:33Multi repositories
- 10:54Reality, it's still a monolith...
- 13:06Is a monolith really bad?
- 14:57API in a Monolith, ingredients?
- 15:40API in a Monolith, really?
- 16:46API in a Monolith, coming soon
- 18:18API Gateway + Monolith MONOLITH
- 18:49OSS API Gateway
- 20:09Spring Cloud Gateway
- 21:52"Release" API Service
- 22:39Internal Cross-Services Comm
- 26:30Monolithic API Platform, done?
- 30:01AUTONOMOUS ALIGNED TEAMS
- 41:27Logs
- 46:42Conclusion
related talks
29mMoving from A and B to ~150 microservices, the journey and learnings
57mSplitting Monolith Application to Microservices
45mHow we rebuild a legacy monolithic platform at CERN and still sleep at night
23mOn the road from Monolith to Micro
51mMicroservices and Microfrontends: Scaling, Learning, Growing
28mThe journey from monolith to microservices
30mMonolith to Microservices
25mBreak up Monoliths and lay them to REST!