Learning bite
Map the cloud operating boundary
Separate application responsibilities from provider responsibilities.
Predict before you try
Does choosing a managed database establish that a deposit works?
Try it: Work through the MicroBank example →On this page
MicroBank in this path
Illustrative design: a public URL does not identify every backend or prove deployment. Customer application, configuration, access and recovery decisions remain explicit when managed-service responsibilities shift.
Open the diagram at full size.
The operating question
A cloud service takes over particular responsibilities; it does not take ownership of the whole application. For MicroBank, distinguish the application processes, their data, the messaging services, access control, and the user-visible transaction result. A managed database changes who operates the database infrastructure, while the application still needs an appropriate schema, queries, connection handling, and recovery decisions. The local emulator is a different operating environment and needs its own inventory.
Work through the MicroBank example
Draw a table with component, operator, configuration owner, verification, and recovery owner. Fill one row for Accounts, one for the database, and one for the message route. Label an unimplemented cloud target as a design.
A worked responsibility record could start like this. These are proposed assignments, not a report of a running cloud environment:
| Component | Service/operator responsibility | Application team responsibility | Evidence to retain |
|---|---|---|---|
| Accounts runtime | Operate the chosen compute service within its contract | Image, configuration, API access, and error handling | Selected image and a checked request |
| Managed PostgreSQL | Operate the database service within the selected plan | Schema, database roles, connection budget, and restore verification | Restored known records in a separate target |
| SNS/SQS route | Operate the managed messaging APIs | Topic/queue policy, consumer envelope, retries, and lifecycle | One case traced through the intended queue |
The provider operating a service does not establish that the application's configuration is correct.
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 choosing a managed database establish that a deposit works? No. It changes an operating boundary; the transaction still needs application verification.
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. It changes an operating boundary; the transaction still needs application verification.
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.
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.