@startuml
Alice -> Bob: Authentication Request
Bob --> Alice: Authentication Response
Alice -> Bob: Another authentication Request
Alice <-- Bob: Another authentication Response
@enduml
https://plantuml.com/sequence-diagram @startuml
Alice -> Bob: Authentication Request
Bob --> Alice: Authentication Response
Alice -> Bob: Another authentication Request
Alice <-- Bob: Another authentication Response
@enduml
https://plantuml.com/sequence-diagram ```mermaid
graph TD;
A-->B
```
Many things that support markdown (e.g. github, gitlab, typora, ...) will render the resulting graph.running directly in the browser is, imho, the best feature of mermaidjs
As a bonus, niolesk is a very good frontend on top of kroki. You get an editable link of your diagram which you can share with teammates.
You can find docker image on github running kroki and niolesk.
And why do so many tools choose to ignore life lines and provide incomplete sequence diagrams? Perhaps it gets really complicated to express in such a simple way as the examples do?
https://plantuml.com/sequence-diagram#5cc0040514e70f7b
You can even have two active on the same lane at the same time, as shown in the second example on that page.
However, it gets to be difficult to use if you've got complicated scenarios. It's very difficult to depict parallelism with PlantUML.
I'd use whichever works for your ecosystem and diagram lifecycle. The syntax is similar enough that I think the diagram creation constraints are often a bigger difference.