Blog
Mert Özen's blog posts on software development, backend, frontend, and DevOps.
Sequence Diagrams 2: alt, opt, loop, par, break and ref for Error Paths and Async Flows
Combined fragments add conditions (alt, opt), early exit (break), repetition (loop), parallelism (par) and indivisibility (critical) to a sequence diagram, while ref calls another diagram; an asynchronous message has an open arrowhead and stays asynchronous even when awaited if the sender does not wait for the result. The post draws the HR Portal approval flow, the insufficient balance error and the e-mail and calendar entry sent through a queue from the real code.
Sequence Diagrams 1: Lifelines, Message Types, Activation and the Journey of an API Request
A sequence diagram shows the messages between participants in one scenario in time order: lifelines side by side, time flowing down, synchronous calls with filled arrowheads and replies with dashed lines. The post draws the HR Portal's POST /leave-requests request from Angular to SQL Server from the real code and EF Core log, and gives it as Mermaid code too.