Module and service boundaries
Find the seams where a system naturally splits, before distributing anything.
Learning path
System boundaries and integration
Design the contracts and edges where independent systems meet and evolve.
0of 10 available now
Start here
Get started
This path is coming soon.
In order
Topics.
Coming soon
API design: REST, RPC, and events
Pick an interaction style from the coupling it creates, not from fashion.
Event-driven fundamentals
Publish facts instead of commands, and accept the consequences.
Integrating external APIs
Depend on a system you do not control without inheriting its failures.
Versioning and backwards compatibility
Evolve a contract without breaking the consumers already using it.
Anti-corruption layers and adapters
Keep a foreign model from leaking into the core of your system.
Modular decomposition inside a monolith
Get boundaries and independence without paying for the network.
Monolith to microservices
Extract services incrementally and earn the cost of distribution.
Data ownership and shared databases
Why a shared database is the coupling that outlives every refactor.
Team topology and architecture
How organisation shape constrains architecture, and how to use that.