Modularity at the (micro)service of Orange's customer space
summary
Orange migrated a legacy PHP monolith that handled 15 million unique visitors into domain-driven microservices (packaged in Docker with CI) and Angular micro-frontends. They expose a single shared API for native apps and web, use server-side rendering, lazy-loaded micro-frontends and a design system to solve SSR, CORS and performance, and now deliver about 15 native and 100 web releases per year while the monolith still handles some deep journeys during migration.
AI-written summary · about
chapters (17)
- 0:00Start
- 0:20Coffee
- 0:40Speakers introduction
- 1:17Presentation of the Orange customer space
- 1:59What do we put in the customer's hands?
- 5:43Usage in 2007
- 7:15The architecture of the Orange customer web space
- 13:02Smartphone evolution
- 13:35How does it work on the customer space?
- 14:42Why a blank page?
- 15:52The new architecture
- 17:40Initial issues
- 22:01Observations
- 23:14Why accelerate further?
- 24:22How to slow down even more?
- 33:34Concrete case
- 39:26Conclusion
related talks
43mGo micro with Microservices
29mMoving from A and B to ~150 microservices, the journey and learnings
24mMicrofrontends
23mMicroservices in a Monolith
18mMicroservices Out In the Wild
51mCompetitive retail architecture with microservices
51mMicroservices and Microfrontends: Scaling, Learning, Growing
23mMicroservices within a Monolith