Structurizr Reviews and details

Social recommendations and mentions

• Could someone give me some feedback on my first 2 diagrams?

  You are welcome! It’s a nice way of breaking down problems. You can go one step further and generate them from code using something like Structurizr (https://structurizr.org/) if you want to get fancy. Source: 12 months ago

• System Design How to?

  Regarding documentation, I created the C4 model for visualising software architecture as a way to introduce some structure into architecture diagrams, because even today most of what I see is still ad hoc boxes and arrows, with little thought into what (abstractions) and how (notation) an architecture is described. My own tooling (https://structurizr.org) allows you to create multiple diagrams from a single model,... Source: about 1 year ago

• D2, a text-to-diagram tool and library written in Go

  Would love to see a comparison to structurizr, which is a higher level dsl that essentially renders to any of the other three you're comparing. Source: over 1 year ago

• Diagram as Code

  I just watched a goto conference talk by Simon Brown on https://structurizr.org/. Source: almost 2 years ago

• Diagrams as Code 2.0

  You can look at https://structurizr.org/ for a free version. Source: almost 2 years ago

• How can I document an AWS project?

  You could look at the C4 models (https://c4model.com/) and Structurizr to render them (https://structurizr.org/). Source: almost 2 years ago

• Generate diagram of the current architecture from structured data

  I created something called the C4 model, which is a way to create software architecture diagrams at different levels of abstraction. I also created some tooling called Structurizr, which is a lightweight model-based approach to creating the above diagrams. The Structurizr tooling is predominantly open source, and split into two distinct parts:. Source: over 2 years ago

• A visual C4 model tool for your team

  C4 model creator here ... In a nutshell, the C4 model is: 1. a hierarchical set of abstractions to describe software systems, and 2. a hierarchical set of diagrams to visualise those abstractions. Benefits include it providing teams with a lightweight common vocabulary to describe/visualise software architecture, with the resulting diagrams being "developer-friendly". It's also independent of any specific notation... - Source: Hacker News / over 2 years ago