RFCs and design docs
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
get a change reviewed before building it.
Planned topics
- Use an RFC for changes that are costly to reverse or cross team boundaries.
- Outline: problem, goals and non-goals, proposal, alternatives, risks, rollout, open questions.
- Keep it short; the aim is feedback, not approval theater.
- Set a review deadline and name reviewers, including consumers of the change.
- Accepted RFCs may spawn ADRs; the RFC explores, the ADR records the outcome.
Draft outline details
Demonstration
an outline for "RFC: move payments to its own service" with non-goals and a rollout plan.
Check your understanding
What is a non-goal for?
Show answer
To state what the proposal deliberately does not try to solve.
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.