Solid Modularization - Untangling the dependency graph
summary
Tinder measures its Gradle graph with Graph Assert and visualizes it in Gephi, finding 598 modules, 4,389 dependencies and a height of 24; CI fails on rule violations and records metrics (height, betweenness centrality) via JGraphT. Analysis spots high‑betweenness “core” modules, so teams extract abstractions—e.g., pull a Result class into core‑result and repository interfaces into core‑data‑public—which shortens longest paths and reduces module influence across the build.
AI-written summary · about
chapters (10)
- 0:00Introduction to modularization
- 3:17Revising modularization strategy
- 5:03Enforcing dependency rules with Graph Assert
- 8:02Visualizing dependency graphs with Gephi
- 10:09Applying graph theory metrics
- 13:40Analyzing problematic modules
- 16:10Case study with Now in Android
- 21:49Refactoring core modules
- 26:44Automating metrics in CI
- 28:28Key recommendations and summary
related talks
37mModularization - flatten your graph and get the real benefits
25mDetangling Your Dependency Graph
32mRoad to modularization
41mBreaking the build
37mA Complete Journey of Android Modularisation
20mBreaking Down Modularization
30mModular Android Development
39mModule Mayhem: Tales From Shared Business Logic