Learning bite
Choose a compute operating contract
Select a runtime by its operating responsibilities and application requirements.
Predict before you try
Does moving the API image to another runtime move the database data too?
Try it: Work through the MicroBank example →On this page
The operating question
Running the same container on another target does not remove the need to configure identity, networking, storage, supervision, and recovery. Begin with MicroBank’s actual process and dependency inventory. Compare a VM service, a container service, and a Kubernetes workload through the work each target leaves with the operator. Use a target because the supported task needs it, not because the diagram has room for another scheduler.
Work through the MicroBank example
Compare two proposed targets in a decision table: supported process model, restart behavior, data dependency, identity mechanism, operational owner, and recovery route. Keep resource sizing and availability requirements as measured or explicitly pending inputs.
Use this small comparison before selecting a target:
| Question | Proposed Linux VM | Proposed managed container service |
|---|---|---|
| What runs Accounts? | A defined process/container under a supervisor | A revision of the Accounts container image |
| Who owns guest maintenance? | The VM operator | The service's documented operating boundary determines this |
| Where does data live? | Explicit external database or separately managed persistent storage | A separately selected persistent data service |
| What proves recovery? | Same saved case after the supervised runtime recovers | Same saved case after replacement or rollback |
Neither column moves a PostgreSQL database merely by starting its API container. Record unresolved sizing rather than inventing a replica count.
Keep the selected source revision and distinguish an illustrative design from actual environment evidence. The teaching reference is MicroBank f75da68 from the implementation guide. Inspect newer application branches before carrying version-specific findings forward.
Compare your reasoning
Does moving the API image to another runtime move the database data too? No. The data and cutover procedure are separate parts of the target contract.
Checkpoint
Save your diagram or decision record, its assumptions, and the next missing verification. No cloud account or provisioning is required for this design bite. Any later cloud run needs its own approved sandbox, scoped identity, cost boundaries, and cleanup evidence.
Read further
Prove what you learned
Inspect the result
Save the component/owner decision, a denied or failed path, and the missing verification.
Explain it in your own words
Explain why your observation supports the stated outcome, and name one thing it does not prove.
Try a small variation
Change one design requirement and revise only the affected decisions; state the trade-off.
Your evidence should show
- Record the context/revision or label the work as a paper or prepared fixture.
- Compare the prediction with the actual result from “Work through the MicroBank example”.
- Save the component/owner decision, a denied or failed path, and the missing verification.
- Explain the transfer challenge and retain the same verification question.
Hint
Separate runtime, identity, network, data, messaging and recovery ownership.
Answer guide: compare after predicting
No. The data and cutover procedure are separate parts of the target contract.
Compare this with your actual observation. A paper answer is useful reasoning practice; record execution separately.
Recall the source-derived MicroBank component map and cloud service responsibility model. Revisit the previous lesson.
Save the prediction, result and explanation ↓Your notes and evidence
Record observations, questions, or links to your work. Keep credentials out of your notes.
Back up or restore this path
Progress and notes stay in this browser. A backup contains only this learning path.