Unit B10-U03 · Backend APIs and integrated services
Databases, transactions, and storage
Persist state without inconsistent partial updates.
Outline only
This is an outline, not a lesson yet
The full lesson for this unit has not been written. This page shows what it is planned to teach, how long it is planned to take, and the reading chosen to support it. No explanation, worked example, quiz or task is published for it yet. See content status.
Planned outcome
Persist state without inconsistent partial updates.
How it would be assessed
Assessed outcome: Persist state without inconsistent partial updates.
Evidence: A task artifact demonstrating the stated action, a verification or comparison record, and a short explanation of uncertainty or failure. Use a new input for the completion check. Allocate the scheduled time across reading, demonstration, lab, quiz, and feedback rather than treating it as reading alone.
Planned time and place
- Planned time
- 3.33333 h in total, including practice and assessment (a planning figure, not tested with learners)
- Module
- B10: Backend APIs and integrated services
- Chapter
- B10-C02: Persistence and execution
- Prerequisite modules
- D20, D30
- Used in programs
- P06, P07
Selected reading for this topic
Core reading
- PostgreSQL tutorial Tables, querying, joins, and transactions; match installed database version.Try it: Persist state without inconsistent partial updates.About this reference (W11)
Optional
- Designing Data-Intensive Applications Data models, transactions, reliability, and distributed-system tradeoffs; use the learner-held edition index.Try it: Persist state without inconsistent partial updates.About this reference (B08)
Reading is chosen to support the outcome; none of it is compulsory homework. Links go to the owners' own sites and some resources cost money. Reviewed 2026-11-17.