{"id":9510,"date":"2022-11-22T09:40:45","date_gmt":"2022-11-22T14:40:45","guid":{"rendered":"https:\/\/blogs.pacasmayo.com\/felipe\/?p=9510"},"modified":"2022-11-24T10:48:42","modified_gmt":"2022-11-24T15:48:42","slug":"plantuml-is-king","status":"publish","type":"post","link":"https:\/\/blogs.pacasmayo.com\/felipe\/2022\/11\/22\/plantuml-is-king\/","title":{"rendered":"PlantUML is king"},"content":{"rendered":"\n

Leer en Espa\u00f1ol<\/a><\/p>\n\n\n\n

If we have chatted for more than ten minutes, you’ve probably heard me mention PlantUML<\/a> once or twice :). And it is because PlantUML is one of the most versatile tools that I have found in my life. It doesn’t matter if I’m programming in C++, NodeJS, Flutter, Helm, Terraform, or even creating an API with swagger, PlantUML is somewhere out there helping me document. One of PlantUML’s biggest advantages is its ability to create diagrams with textual instructions, and consequently versionable. That is, I don’t have to change my programmer’s hat and put on an artist’s hat to create the graphs and diagrams that will accompany my code, but rather they are created at the same time, and they stay fresh through all the evolutions of the code.<\/p>\n\n\n\n

Code in PlantUML<\/td>Results<\/td><\/tr>
@startuml
rectangle \"Reusable designs\\n=====\\nArchitects create the blueprint once\" {   
  actor \"ISO\" as iso2   
  actor Network as network2
  actor DevOps as devops2 
  actor Storage as storage2 
  [Blueprint] as bp2 
  [Solution1] as s1 
  [Solution2] as s2 
} 
iso2 -> bp2 
network2 --> bp2 
devops2 --> bp2 
bp2 <- storage2 
bp2 --> s1 
bp2 --> s2 
@enduml<\/pre><\/td>
<\/td><\/tr>
@startuml
!include <C4\/C4_Container>
title Some Network Automation\\nApplication Architecture\\nC4 Container
System_Boundary(ssys,Some Network Automation){
  Container(sys,Some Network Automation,NodeJS,In-house developed Network Automation)
  Container(bull,Bull Queue,Redis\/NodeJS,Queuing engine)
  ContainerDb(redis,Redis,Caching DB)
}
System_Ext(nac,Network Product,Network Access Control)
System_Ext(mdm,MDM,Device management system)
System_Ext(dns,DNS,DNS & DHCP management system)
System_Ext(cmdb,CMDB,\"CMDB, Change Management\")
BiRel_R(sys,nac,Reads network devices and writes new role,HTTPS)
Rel(mdm,sys,Reads IPTV devices,HTTPS)
Rel(sys,dns,Writes DHCP reservation,HTTPS)
BiRel(bull,sys,Reads events and writes status,Queue)
BiRel(sys,redis,Reads and Writes lists,Redis,port 6379)
BiRel(bull,redis,Reads and Writes queues,Redis,port 6379)
Rel(sys,cmdb,Writes informational events)
SHOW_LEGEND()
@enduml<\/pre><\/td>
<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

I even use it to illustrate my theology courses at the University, or the sermons in the church.<\/p>\n\n\n\n

@startuml
skinparam backgroundColor transparent
(Herodes el Grande) as grande
together {
  (Herodes Antipas) as antipas #pink
  (\"Herodes II - Felipe\") as felipe
  (Arist\u00f3bulo) as aristobulo
}
(Herod\u00edas) as herodias
(Herodes Agripa) as agripa
grande --> antipas
grande --> aristobulo
grande --> felipe
aristobulo --> herodias
aristobulo --> agripa
felipe <.. herodias #line:green;line.dotted
antipas <.. herodias #line:red;line.dashed;text:red
@enduml<\/pre><\/td>
<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Also, almost all markdown systems have built-in template support, or it’s available with a plugin. For example,<\/p>\n\n\n\n

markdown<\/td>resultado en HTML<\/td><\/tr>
# Sequence Diagram

## Example
```plantuml
@startuml
actor user
control proxy
entity programa
database database
user -> proxy++ : login
proxy -> programa++ : login
programa -> database++ : existe el usuario
database --> programa-- : si
programa -> database++ : consigue actividad del usuario
database --> programa--
programa --> proxy-- : muestra la actividad
proxy --> user--
@enduml
```
## Advantages
- First
- Second<\/pre><\/td>

Sequence Diagram<\/h1>

Example<\/h2>

Advantages<\/h2>