The Architectures course is live
Building Maintainable PHP Applications: Architectures is live. All 15 lessons in its 5 chapters are published, and the course is free. It's the third of six courses in the series, and it's marked advanced.
What the course is about
Foundations covered how to think about code that has to keep changing. Patterns and Principles covered the small tools. Architectures is about the shape of the whole application.
The first lesson opens with a codebase that adopted Hexagonal Architecture because it sounded professional. A one-line change to a form field touches a request object, a use case, a port and its adapter before it reaches the reservations table. The course teaches the layers and where each one earns its place, so you can avoid building that codebase.
A deliberate architecture pays off when several of these are true at once:
- Many delivery mechanisms trigger the same use case: HTTP, a queue worker, a scheduled job, a webhook, a CLI command.
- The test suite can't reach business logic without booting the framework.
- The team is large enough that "where does this go?" costs real time.
- The product should outlive its current framework major version.
- You can afford the up-front cost.
Brand sites, CRUD admin tools and side projects run by one or two people don't need it. For those, the first two courses cover most of what you need.
What's inside
| Chapter | Lessons | What it covers |
|---|---|---|
| When You Actually Need This | 1 | Whether your project's entry points, test pain, team size and lifespan justify a deliberate architecture |
| Architectural Styles | 2 to 8 | Layers and the dependency rule, the request lifecycle, Hexagonal, Clean and Vertical Slice architecture compared, and Action-Domain-Responder |
| Living With an Architecture | 9 to 12 | Where framework code is allowed to live, testing across the boundary, module boundaries in a modular monolith, and a different style per module |
| Applying It to Real Projects | 13 to 14 | Migrating a legacy PHP app step by step, and the Strangler Fig pattern |
| Putting It Together | 15 | A capstone that turns a two-year-old legacy Laravel app into a modular monolith of ports, adapters and vertical slices |
One codebase from start to finish
From the second lesson on, the examples belong to Hearth, a hotel booking app built in Laravel under the Hearth\ namespace. Each style is shown on the same features, so you can compare them on code you already know. The capstone restructures Hearth around ports, slices and modules.
What comes next
Domain-Driven Design is the fourth course in the series. It fills the shape that Architectures gives the application with a model of the business: bounded contexts, ubiquitous language, entities, aggregates, Event Storming and Anti-Corruption Layers.
Free content keeps coming
Insights and quick tips stay free to read, and new free courses, learning paths, code reviews, insights, quick tips and projects keep being released alongside the paid catalogue.
Follow along
New content is announced on X, Bluesky, LinkedIn, Facebook, Instagram, as well as the newsletter as it publishes.