Contract-first parallel delivery
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
let teams build at the same time by agreeing interfaces first.
Planned topics
- Contract-first: write the API schema or event schema, agree it, then both sides build against it.
- Stubs and mocks generated from the contract let the consumer start before the provider is ready.
- Contract tests catch drift: provider and consumer both verify against the agreed schema.
- Feature flags let unfinished work merge and deploy without being visible; integration turns on in stages.
- Changes to a contract go through a visible, versioned process.
Draft outline details
Demonstration
Timeline of two teams: week 1 agree the schema; weeks 2-4 provider builds, consumer builds against a stub; week 5 swap stub for the real service behind a flag. Mention schema tooling by role (OpenAPI, an event schema registry); verify tool versions before recording.
Check your understanding
What lets a consumer start before the provider has finished?
Show answer
A contract-derived stub or mock.
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.