Building Spring Boot based modular libraries for 120 teams our findings
summary
Ocado Technology built a Spring Boot modular library ecosystem used by more than 120 teams and over 400 production applications, split into 90 modules maintained by a seven‑person custodian team plus contributors (132 historic) and driven by runtime telemetry into Looker Studio dashboards. Releases run at ~200 releases per year, testing uses sandbox apps, LocalStack/Testcontainers, dependency-diff checks and automated condition‑evaluation tests, and the modular, one‑thing‑per‑module design plus community governance results in steady adoption and manageable upgrades.
AI-written summary · about
chapters (22)
- 0:00Start
- 6:47The ecosystem
- 7:34The technologies
- 9:08The user build
- 10:24How do we make it work for 120 teams
- 11:14Characteristics mixer - design
- 12:07Characteristics mixer - dynamics
- 13:11Characteristics mixer - community
- 16:20Being custodians
- 17:17Analysing usage data
- 18:342. Example: supporting the decision process
- 20:242. Example: users discovery
- 22:23Interacting with people
- 24:42Creating narration
- 26:13Working with the community
- 27:50Domain design - overview
- 29:58Domain design - evolution
- 31:07Module design
- 38:45Software design
- 39:21Engineering practices
- 46:41Agile release model
- 48:17Agile documentation - overview
related talks
46mModular Applications with Spring
46mFrom Chaos to Cohesion: Building Modular Monoliths in the Real World
01h 11mSpring Modulith – Spring for the Architecturally Curious Developer
51mMicroservices and Microfrontends: Scaling, Learning, Growing
28mManaging a team building a modular monolith in Laravel
45mHow we rebuild a legacy monolithic platform at CERN and still sleep at night
10mModular Architecture
35mThe Great Modularization: How We Scaled a 15-Team React Native App Without Losing