Level up with a Microservices architecture
summary
Argues for designing clear domain packages with DDD and CQRS, then packaging them so they run together now but can be split later, showing concrete tools: PHP packages, composer, mono‑repo/mini‑repo, Docker, CI, MongoDB and a message bus (NATS/Rabbit/SQS) for async listeners. Gives numbers—about 60 repositories and a tiny team (~4 PHP devs)—and shows builds: domain APIs, infrastructure bindings, an aggregator package and command and event bus flows; result is faster responses and safe, incremental extraction.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:30About me
- 2:30The plan
- 3:40Motivation
- 6:50Myths
- 9:05Key Concepts
- 12:40Request Journey
- 15:25Using Prezi
- 23:05Other ingredients
- 24:50Benefits
- 29:13Incremental plan
- 31:05More code
related talks
43mGo micro with Microservices
40mDDD, CQRS, Hexagonal, Onion,... Putting it together
52mBuilding monolith applications that could scale to microservices..
52mI Have a Microservices Architecture and I Didn't Know.
46mPackage Development
37mKnee Deep in Microservices
29mDevOps and Microservices Better Together
52mMicroservices: A Utopian Mystery