Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
15 results for “Sequence Diagrams”
Sequence Diagram
A diagram showing the ordered exchange of messages between participants over time, used to make an interaction's control flow and failure points explicit.
C4 Model
A set of four nested diagram levels — context, container, component, code — that keeps each diagram at one consistent level of abstraction.
Consistent Prefix Read
A guarantee that if a sequence of writes happens in a given order, a reader sees a prefix of that sequence — never an out-of-order subset.
Cross-Zone Data Transfer
Charges incurred when data moves between availability zones within a region — invisible on architecture diagrams and a recurring surprise on cloud bills.
Data-Flow Diagram
A diagram of how data moves between processes, stores and external entities, with trust boundaries drawn on it.
Event Sourcing
Storing the full sequence of state-changing events as the system of record, and deriving current state by replaying them.
Message Ordering
The guarantee about the sequence in which messages are delivered — normally per-partition or per-group only, and lost the moment consumption is parallelised.
Saga
A sequence of local transactions across services where each step has a compensating action that semantically undoes it if a later step fails.
Value Stream
The end-to-end sequence of activities that delivers a result to a customer, viewed across whatever departments and systems it happens to cross.
Sequence Diagrams
Ordered message exchange, and walking the failure of each arrow.
Architecture Diagrams
Choosing an audience and refusing to mix levels of abstraction.
Context Diagrams
The system as one box, with its users and external systems.
Data-Flow Diagrams
Following the data across trust boundaries rather than the calls.
Deployment Diagrams
What runs where, in which zone, behind which boundary.
C4 Model
Context, container, component and code as four separate diagrams.