Reading up on C4 Model...how would you document related systems and repos without repeating yourself?

This page summarizes the projects mentioned and recommended in the original post on /r/softwarearchitecture

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • dsl

    Discontinued Structurizr DSL

    Create a system landscape, plus a drill-down for each system. In this option you create a new repo in which you define your system landscape - i.e. all of the people and software systems, plus their interactions. In the system1 repo, you extend this model to add the internal details, diagrams, and docs specifically for system1. Repeat for system2 and system3. With this approach, you would see that system1 (and system1.serviceX) interacts with system2, but you wouldn't see system2.serviceY, since that's an implementation detail of, and internal to, system2. The Structurizr DSL has been designed to work for this use case with the "workspace extension" feature, see https://github.com/structurizr/dsl/tree/master/docs/cookbook/workspace-extension for more details.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts