Module · Backend Engineer
Service Design & Reliability
Draw the boundaries, own the data, and be ready for the day the service is on fire.
TOPIC 01
Boundaries & Contracts
Who owns which table, and what the services say to each other.
What you'll practice
- Draw the Service Boundaries — guided · beginner
- Publish the Event Contracts — practice · intermediate
A command you'll meet
cat ~/backend/services/README.mdTwo services writing one table is two services with one bug. Open the task below for the full walkthrough.
Hands-On Tasks in This Topic (2)
Draw the Service Boundaries
A boundary is a promise about who may change what. Write it down for the two services, including which one owns each table.
Publish the Event Contracts
An event is a promise to every consumer, present and future. Write the contract with the version, the schema and the owner.
TOPIC 02
Production Readiness
Health checks, objectives and the migration that does not break the old version.
What you'll practice
- Pass the Readiness Checklist — practice · intermediate
- Change the Contract Safely — challenge · advanced
A command you'll meet
cat ~/backend/services/readiness.mdThe checklist is what stops a rushed release. Open the task below for the full walkthrough.
Hands-On Tasks in This Topic (2)
Pass the Readiness Checklist
A service is ready when it can be observed, alerted on and run by somebody else at 3am. Write the checklist it has to pass.
Change the Contract Safely
Old clients and new servers have to coexist for at least one deployment. Write the expand and contract plan that makes that possible.