Automatic C4 diagrams for a distributed microservice ecosystem with GitHub Actions

1. architecture

   1 1 8 0.0 Shell

   📓 Components and relations (by acme-corp-tech)

   

   @startuml "cart_components" !include https://raw.githubusercontent.com/plantuml-stdlib/C4-PlantUML/master/C4_Container.puml System_Boundary(cart_system, "[[https://github.com/acme-corp-tech/architecture/wiki/cart_system.svg Shopping cart]]") { Container(cart_service, "Cart Service", "Go", "Tracks cart contents", $sprite="go") ContainerDb(cart_storage, "Cart Service Storage", "Redis", "", $sprite="redis") } @enduml

2. SaaSHub

   www.saashub.com featured

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

3. cart

   2 1 0 0.0 Go

   🛒 Cart service (by acme-corp-tech)

   

   Each documented entity (microservice repository) contains own diagram fragments at ./resources/diagrams.

4. service-starter-kit

   3 1 2 0.0 Go

   🏘️ Go service template

   

   Template workflow to trigger an update whenever fragment is changed: https://github.com/acme-corp-tech/service-starter-kit/blob/master/.github/workflows/diagrams.yml.

5. C4-PlantUML

   4 26 6,522 6.5 PlantUML

   C4-PlantUML combines the benefits of PlantUML and the C4 model for providing a simple way of describing and communicate software architectures

   

   C4 PlantUML

6. workflow-dispatch

   5 1 336 5.2 TypeScript

   A GitHub Action for triggering workflows, using the `workflow_dispatch` event

   

   GitHub Action for Dispatching Workflows benc-uk/workflow-dispatch

Suggest a related project