Criteria for extracting a service
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
apply concrete criteria, not fashion.
Planned topics
- Extract when there is a real driver: independent scaling backed by load data, a different release cadence, a team boundary, a different availability or compliance need.
- Check readiness: clear bounded context, owned data, a stable API, few callers.
- Check capability: monitoring, CI/CD, and on-call exist.
- "Not extracting" is a valid decision; modular monolith first (MID-059).
- Record the decision as an ADR with the criteria and the date to revisit.
Draft outline details
Demonstration
a scoring table: driver, data ownership, coupling, team, operational readiness, each yes/no/unknown.
Check your understanding
Is "keep it in the monolith" an acceptable outcome?
Show answer
Yes, when justified.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.