Modularization - How hard can it be?
summary
Spotify breaks a giant Android monolith into hundreds of modules, starting with a core team that spends two months to get one feature outside the monolith and reduces unit test time from minutes to tests run in under five seconds. The process uses Gradle with caching, a strict module layout and iterative dependency inversion, scales to about 700 modules, makes subsequent features take 2–3 days to extract, and shrinks the main module to roughly 200k lines while assembly still takes a few minutes.
AI-written summary · about
chapters (6)
- 0:00Start
- 25:09BUILD TIMES?
- 28:48Modularization is a chance to tackle tech debt
- 31:03Modularization How hard can it be?
- 31:15Software development How hard can it be?
- 31:49#OddlySatisfying
related talks
41mMODULARIZATION HOW HARD CAN IT BE
37mA Complete Journey of Android Modularisation
32mRoad to modularization
39mScaling an Android App from 1 to 100 developers with modularization.
27mModularising the right way
30mModular Android Development
52mmulti-module Android application
34mIntro to App Modularization