Architecture, Performance, and Operations at Scale
For the mid-to-senior Laravel engineer who already knows how to build an application and is now the one handed the architecture decisions, the performance incident, and the migration that has to happen without a maintenance window.
If you’re looking for how to define a route, write a migration, or use Eloquent relationships, there are excellent books for that already - this isn’t one of them. This book starts where those end.
NOT IN HERE
WHAT’S ACTUALLY IN HERE
Part 1 and Part 2 build vocabulary the rest of the book assumes. Beyond that, most parts stand on their own - if you picked this up because of a live incident with your queues, your database failover, or your CI pipeline, it’s reasonable to skip straight to the relevant chapter.
Structuring Laravel Systems
Sets the vocabulary and decision frameworks the rest of the book relies on - establishing that “monolith vs. microservices” is really several independent decisions that get conflated into one.
The mechanics of making a Laravel application fast under real load, from the database up through the caching and queue layers.
Performance and availability don’t matter if the system produces wrong answers under concurrency - idempotency, state machines, and ledger patterns for systems where the mistake is money.
Keeping the system up, or gracefully degraded, when a dependency fails, a data center goes dark, or a risky release needs to be undone in seconds instead of minutes.
Seeing what a production system is actually doing - logs, metrics, and traces that answer “what happened,” and alerts that page on what users feel.
Getting code from a merged pull request into production safely and repeatably - build pipelines, container-based releases, and the infrastructure underneath them.
The day-to-day discipline of running a live system: closing the security gaps behind most real incidents, responding well when something breaks anyway, and managing cost sustainably.
One fictional system, HaatBazaar, followed through every layer this book has covered, as the decisions from Parts 1 through 7 collide during a genuinely bad night.
The full chapter list, if you’d rather scan titles than descriptions. Plus a preface up front and, at the back, an appendix with a glossary and an about-the-author page.
The sample includes the front matter, the complete table of contents, and Chapter 8 in full - enough to see both how the book opens and how a full chapter reads. No email required.
IN THE SAMPLE
The book is almost done and coming soon. Leave your email and I’ll send one note, the day it’s ready. No spam, no drip campaign.
Nuruzzaman Milon is a software engineering leader, open-source creator, and tech community organizer living in the Pacific Northwest. With a professional background spanning international tech hubs across Europe and North America, he balances his technical work with a love for traditional cooking, residential gardening, and personal digital archiving. He lives near Vancouver with his wife and three children.
More at milon.im →