logo

Developers eXperience . Architecture Diagrams for mortals . C4 & C5 diagrams as code

time2 yr agoview0 views

So for me, Developer eXperience - is not about DevOps or pipelines it crucial but the most critical for me is the cognitive load of understanding systems. The cognitive load that developers have while interacting with a system. The biggest impedance of all modern systems - is the gap between solution architecture and code. Even architects have to use the elevator https://www.amazon.de/-/en/Gregor-Hohpe/dp/1492077542/ref=sr_1_1?keywords=architecture+elevator&qid=1652627477&sprefix=architeture+e%2Caps%2C80&sr=8-1 to meet solution-application gap For this, we are still hoping for 5th generation languages but to survive with the instruments that we currently have, we use models. All models are wrong, but some of them are useful. So C4 diagrams https://c4model.com/ and C5 (C4+ connection diagrams) give us a drill-down view from systems and users to components and classes and lower cognitive load and represent a system in a digestible human-friendly way We use https://github.com/plantuml-stdlib/C4-PlantUML, so all our diagrams are versioned code, and if you are a lucky user of GitLab all your diagrams cold be embedded and rendered out of the box from MD files. One suggestion there - focus not on real infrastructure connections, focus on logical relations and put all plumbing into a connection diagram. More you could find in my video For fans of books - https://leanpub.com/b/software-architecture

Loading comments...