Build software like a bag of marbles, not a castle of LEGO®
summary
Argues for modularizing features as drop-in assemblies rather than tightly coupled layers, showing a concrete approach: use onion architecture for a core with no framework references, scan deployment DLLs for type-registrars to wire a DI wrapper, load controllers via ASP.NET Core application parts, resolve feature handlers with a scoped service locator, extend the EF model at runtime via OnModelCreating, and handle migrations either centrally (rename the __EFMigrationsHistory table at deploy) or per-plugin with FluentMigrator or careful runtime migration sequencing.
AI-written summary · about
chapters (10)
- 0:00Start
- 8:39Layers
- 14:56Challenges
- 17:13Onion architecture
- 17:57Onion Concepts
- 23:09Example integration DI
- 30:10ASP.NET Core
- 35:08Entity Framework Core
- 39:29Migrations: 2 approaches
- 46:26Conclusion
related talks
54mBuild software like a bag of marbles, not a castle of LEGO®
50mBuild Software Like a Bag of Marbles, Not a Castle of LEGO
58mBuilding that glorious monolith. And carving it too.
01h 04mPractical advice for building glorious monoliths
54mDesigning for change with Vertical Slice Architecture
01h 02mBuilding that glorious monolith. And carving it too.
41mUsing Boundary-Driven Development to beat code complexity
42mFlutter Engineering, Architectural path