Evaluating a boundary
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
test a proposed boundary with questions.
Planned topics
- Do changes usually stay inside one service? Look at change history for co-changing files.
- Does a typical use case need one service or five? Many hops signal a bad cut.
- Can the service work if others are down?
- Is the data owned by exactly one service?
- Is there a team that can own it and a stable API?
- Wrong boundary signs: chatty calls, lockstep releases, shared tables.
Draft outline details
Demonstration
a checklist table with columns Criterion, Evidence, Pass/Fail.
Check your understanding
Which sign shows a bad boundary?
Show answer
Chatty calls, lockstep releases, or shared tables.
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.