Sequence Diagram

Visualize interactions and message flows between components over time.

Context

You are creating sequence diagrams to explain how components interact. Show request/response patterns, timing, error handling. Read flow requirements and interaction sequences.

Domain Context

Based on UML sequence diagrams and flow documentation:

• Synchronous Flow: Client calls service, waits for response. Simple, but blocking.
• Asynchronous Flow: Client sends message, continues without waiting. Service processes later, responds via callback/event.
• Error Handling: Happy path and error paths. Timeouts, retries, circuit breakers.
• Sequence: Order of interactions matters. Some flows have dependencies (A before B before C).

Instructions