Skip to content

docs(diagrams): adding diagrams for call, flow, and sub-package structure#791

Open
stephan-rayner wants to merge 2 commits intomainfrom
stephan-rayner/docs/add-call-diagrams
Open

docs(diagrams): adding diagrams for call, flow, and sub-package structure#791
stephan-rayner wants to merge 2 commits intomainfrom
stephan-rayner/docs/add-call-diagrams

Conversation

@stephan-rayner
Copy link

No description provided.

@stephan-rayner stephan-rayner self-assigned this Feb 17, 2026
@stephan-rayner stephan-rayner requested a review from a team as a code owner February 17, 2026 23:18
@stephan-rayner stephan-rayner added documentation Improvements or additions to documentation area/monitoring labels Feb 17, 2026
@stephan-rayner
Copy link
Author

stephan-rayner commented Feb 17, 2026

@nikimanoledaki could I trouble you particularly to take a look at this one. I imagine you may know this well enough to know if I missed anything. I typically make something like this to help me understand a project better 😄

Copy link
Contributor

@nikimanoledaki nikimanoledaki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The diagrams and info is all correct 👍 😄 It's nice to have a visualisation for this!

My only concern is how this diagram will scale as we add more services for each provider. One way we could solve this is by showing a single service per provider as an example rather than a list of all of them. There are some outliers though like the AWS EC2 service, which has some unique stuff compared to the other ones. We could generalise the flow enough that it covers them all. WDYT?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/monitoring documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments