"Modulitiche" Applications
summary
Presents a “modulitic” architecture between monolith and microservices and a concrete Laravel app split into four Composer packages (domain, core, db-access, ui) wired with service providers. Shows dependency injection of interfaces to implementations, how to replace the data backend by creating an alternative package and updating Composer, and demonstrates swapping packages via Composer changes the site without touching the application code.
AI-written summary · about
chapters (10)
- 0:00Start
- 8:51The Two Extremes: Monolith vs Microservices
- 9:35Advantages / Disadvantages
- 12:56From Monolith to Modulith
- 13:48Two Applications, Single Model
- 15:01Extending Applications
- 15:39Customizing Applications
- 16:25Conway's Law
- 22:07Independence from Details - Dependency Inversion
- 33:25Missing Pieces
related talks
34mMateus Guimarães :: Unveiling the Modular Monolith
37mLife Beyond Microservices: Modular Monoliths in Laravel
40mEngineering Complex Applications with Laravel 4
40mFrameworkless – The New Black?
32mDesign Patterns and Packages for Excellent Laravel Backoffices
34mLevel up with a Microservices architecture
31mModern PHP development with Laravel 5.6
28mManaging a team building a modular monolith in Laravel