Forging the path from monolith to multi-module app
summary
The TIER app evolves from a single monolith into a layered multi‑module structure over about a year (discussion starts July 2021, first UI module merged May 2022), splitting shared code into a small shell module, creating client modules with contract / implementation / mock triples, and extracting features gradually. A custom Gradle plugin enforces boundaries, a navigation SDK hides activity/fragment details, and Gradle version catalogs plus convention plugins automate setup. Result: much faster incremental builds, clearer ownership, legacy module shrinking and reproducible developer workflows.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:24Decide your architecture
- 19:33Rethink Navigation
- 28:42Improve Gradle Setup
- 31:30Restart doing things
related talks
39mForging the path from monolith to multi-module app
37mForging the path from monolith to multi-module app
39mModule Mayhem: Tales From Shared Business Logic
32mRoad to modularization
37mA Complete Journey of Android Modularisation
46mFrom Chaos to Cohesion: Building Modular Monoliths in the Real World
40mModularizing Android Applications
20mBreaking Down Modularization