Organisational change centered around technology
summary
A three‑year transformation moves a monolith to microservices on public cloud using the Strangler pattern and a lighthouse team isolated to prove the approach; production features ship in months with no test environment by relying on feature flags and incremental front‑end composition; front ends split by route with CDN/nginx routing and shared libraries; a composure project composure on GitHub implements edge‑style fragment composition; beware 20‑minute front‑end builds and pick very small MVPs to prove cultural change.
AI-written summary · about
chapters (32)
- 0:00Introduction
- 1:15Digital transformation
- 2:15Changing business model
- 3:20Going through the organisation
- 4:35Starting at tears
- 6:08Getting the team in isolation
- 6:56The founders are very enlightened
- 8:54Technology DNA
- 10:37Communication
- 11:25Emergent organizational structure
- 13:16War zone
- 13:48Interim period
- 14:12Pick the right thing
- 14:57Make a mistake
- 16:11Minimum Viable Product
- 16:31Management Structure
- 17:19Ownership and Leadership
- 18:55seize the right opportunity
- 19:37start small
- 20:18pods
- 21:54team autonomy
- 23:08hiring decisions
- 24:00team fit
- 27:23frontend composition
- 32:54disconnected from output
- 33:29team communication
- 33:55beer time
- 34:26microservices
- 35:13mini monolith
- 35:51microservices are too large
- 36:04autonomous teams
- 36:42microservice joke
related talks
30mApplication Modernization Using Cloud Strangler Pattern and DevOps Best Practices
47mFrom Monolith to Microservices With the Strangler Pattern
29mHow to change mindset of coworkers?
23mOn the road from Monolith to Micro
33mFireside chat - Monoliths, Microservices & Modernization – Practical Strategies
27mMicro-transformation
24mMicrofrontends
27mTinkertoys, Microservices, and Feature Management: How to Build for the Future