Growing Spring-based commons, lessons learned
summary
Allegro moves from an opinionated all‑in‑one Spring framework to a set of focused Java libraries plus an optional Spring Boot starter to support 400 services across JVM and non‑JVM apps. The libraries are single‑purpose, technology‑agnostic cores with separate integration modules, minimal dependencies, builder APIs and clear public surfaces; breaking runtime protocols is expensive so readers are updated before writers; for rollout and legacy clients a sidecar process centralizes runtime responsibilities.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:34IT perspective
- 2:58Allinone framework
- 11:39Do one thing well
- 13:48Technology agnostic
- 18:24Minimal dependencies
- 23:01Clear entry points
- 28:03Compatibility
- 33:51Vision
- 38:06No magic
- 40:31Developer friendly
- 44:56Rich environment
