I Learnt Microservices & DDD Almost by Accident

I learnt Microservices & DDD almost by accident 🤯
Over a decade ago, I was part of a complex product build we'd spent a good year building a product that had grown perhaps beyond original intent.
It was a mammoth 🐘
- ✔️ Extensive analysis
- ✔️ Slow deployments
- ✔️ Regression issues
- ✔️ Long test cycles
It slowly turned into a monster 👹 No matter what we threw at it… Nothing really worked.
The architecture was tightly coupled 🔗 Every change felt risky. Every release painful.
It was a bit too late… But we finally paused and did a retrospective 🧠 We sought external feedback.
One reviewer asked a simple question:
"Why didn't you use microservices? Cloud? Events?"
My honest reaction? Micro… what? 😅
But curiosity kicked in.
I created my first AWS account ☁️ I installed Docker 🐳 Kubernetes had just been released I got access to all of it And started building sample apps.
Initially, It felt daunting. It felt complex It was exhausting 😵💫
I struggled.
I had to learn:
- Containers 📦
- Microservices
- Observability 🔍
- Circuit breakers ⚡
- Domain Driven Design
- Event Driven Architecture
- Infrastructure as code ➡️
- CICD Tools ♾️
One of the first use cases?
A loan app with ~50 applications a month.
It felt like massive overkill for a small volume 🙈
But in hindsight…
It gave us a solid foundation 🏗️ Once the first journey was live Onboarding complex journeys became easier Scaling no longer scared us 📈
It took me years to feel comfortable. But once it clicked, it became my default approach.
Now, when a domain starts to grow… I know what to look for.
If you're starting something new:
- 👉 Be patient
- 👉 Keep learning
- 👉 Focus on hands-on experience
- 👉 Architecture reveals itself over time ⏳
Sometimes the best learning journeys start… by accident 🚀