When to merge services back
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
recognize and recommend consolidation.
Planned topics
- Signals: lockstep releases, chatty calls, shared database, one team on-call for both, low independent change.
- Merging reduces network cost, operations, and consistency complexity.
- Merge decisions need the same evidence as split decisions.
- Treat a merge as learning, not failure.
Draft outline details
Demonstration
a scorecard for two chatty services: calls per request, joint deploys, shared data, team overlap.
Check your understanding
Name two signals that services should merge.
Show answer
Lockstep releases and chatty calls, or shared database.
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.