Deployment and operation are design concerns. Configuration, backing services, and process shutdown deserve explicit contracts.
What to look for
- 01
Keep deployment-specific configuration out of application source.
- 02
Make processes robust to restarts and interrupted work.
- 03
Separate build, release, and runtime concerns.
Keep in mind
A historically influential application model. Modern platforms may implement its intentions through different mechanisms; treat each factor as a design question.
Try this next
Choose one service and document where configuration comes from, how a release is identified, and what happens to in-flight work when it stops.
Get the architecture templateNotes and exercises by Awesome CTO. The original work belongs to Adam Wiggins and contributors.
