Principle Six: Modularization and Deep Modules

#177 - Simple Object-Oriented Design: Principles for Writing Maintainable Software - Mauricio Aniche

Topic 13 of 15

Published Jun 3, 2024 · Clip 45:12–48:53 (3:41)

Mauricio explains modularization for large systems with multiple growing domains: modules need to communicate while staying isolated. Borrowing Ousterhout's term, deep modules have a beefy responsibility (e.g., the whole billing domain) and expose a simple interface that hides internal complexity. Avoid millions of modules or microservices; splitting trades gains for losses. Sensible defaults help simplify interfaces, and modules shouldn't leak internal details like database tables.