System evolution and leadership
Migrate live systems and make technical decisions other teams can carry forward.
Change a live system without losing its contract
A storage migration or a cross-team platform decision changes more than one component. These chapters keep the user’s outcome visible while data, clients, ownership, and rollout responsibilities change.
Explain authority, compatibility, repair, rollback, and retirement where they matter. Finish with decisions other engineers can implement and maintain.
Parts group related chapters. Each lesson has a chapter.lesson address, such as 4.07. Open a title below, or use Next to follow the reading sequence. Within a lesson, On this page lists its sections.
- CH 16
Live migrations
Move live data and clients through compatibility, repair, and retirement.
- CH 17
Technical decisions and engineering effectiveness
Make scope, ownership, adoption, and cross-team decisions explicit.