Software architecture under change
Reason from ownership and dependency direction through consistency, capacity, migration, operability and changed-constraint decisions.
20 units · Web, Plus, Pro · 20 programming subjects + 2 security tracks
Branches show this unit’s authored theory, coding and assessment work.
Unit 1 / 20
Reject a stale entity transition at the fact owner
Reject a stale entity transition at the authoritative fact owner before publishing derived views.
0 prerequisite skills · Reading, guided completion and independent success remain separate evidence.
The course, in order
Open a unit in the map to inspect its activities. Reading, guided completion, independent work and review remain distinct evidence.
- Reject a stale entity transition at the fact owner
Reject a stale entity transition at the authoritative fact owner before publishing derived views.
Open this unit - Choose reads from the promised freshness scope
Select a read path that satisfies the caller’s promised freshness scope rather than choosing by convenience.
Open this unit - Give inventory one writer and a separate derived read path
Give inventory changes one authoritative writer and keep derived read ownership separate.
Open this unit - Publish a versioned domain fact without exposing its storage layout
Publish a versioned domain fact whose public contract does not expose private storage representation.
Open this unit - Move policy ownership while keeping a legacy transport adapter compatible
Move domain policy ownership while retaining a compatible legacy transport boundary.
Open this unit - Turn a quality claim into a measurable workload scenario
Turn a qualitative requirement into a measurable workload, response and acceptance scenario.
Open this unit - A decision record includes the rejected alternatives
Record the chosen decision, rejected alternatives and consequences rather than preserving only the conclusion.
Open this unit - Compensate an owned reservation without releasing another operation’s stock
Compensate only the reservation still owned by the failed operation, retaining another accepted owner’s stock.
Open this unit - Invert a storage dependency without moving domain policy into the adapter
Invert a storage dependency without transferring domain policy into its implementation adapter.
Open this unit - Give a renderer only the data and operations its task requires
Give a renderer only the data and capabilities required by its current task.
Open this unit - Keep publication intent and consumer acceptance with their own effects
Keep publication intent and consumer acceptance in the durable boundary that owns their respective effects.
Open this unit - Admit only work that fits both capacity and time
Admit work only when both its capacity demand and deadline fit the declared budget.
Open this unit - Reserve capacity for a lost node without exceeding the shared database pool
Reserve capacity for a failed node without exceeding the database pool shared by surviving nodes.
Open this unit - Contain a failing notification dependency within its reserved pool
Contain a failing notification dependency within its reserved pool so unrelated work remains admissible.
Open this unit - Move one live route without creating two writers
Move a live route through one authoritative writer rather than temporarily creating two competing owners.
Open this unit - Withdraw admission and verify a drain before releasing a measured bottleneck
Withdraw new admission and verify the measured drain before releasing a bottleneck resource.
Open this unit - Enforce a transitive policy boundary while reviewing a plausible module graph
Enforce the transitive dependency policy instead of checking only the immediate module edges.
Open this unit - Retire an old data representation only after compatible readers and references
Retire an old representation only after compatible consumers and retained references no longer require it.
Open this unit - Restore a failed authority before rebuilding its derived consumers
Restore authoritative facts before rebuilding consumers whose state is derived from them.
Open this unit - Resolve competing quality requirements with an explicit cost model
Compare competing quality requirements with an explicit workload and cost model.
Open this unit
