Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: Add a Sankey diagram for system architecture #2368

Open
myearn4 opened this issue Jul 3, 2024 · 3 comments
Open

[Feature]: Add a Sankey diagram for system architecture #2368

myearn4 opened this issue Jul 3, 2024 · 3 comments

Comments

@myearn4
Copy link

myearn4 commented Jul 3, 2024

Requirement

As a software engineer, I'd like to have a better understanding of micro service traffic dependency. The system architecture can help on this purpose at some point. But I think it would be better, if the architecture can be shown in the format of Sankey diagram.

Problem

The current system architecture diagram lacks clarity, especially when displaying tens of microservices. It merges all services together, making it difficult to discern their dependencies.
d5188c0d7569bb55f1fc31c717e2345

A Sankey diagram format would significantly improve clarity by visually representing dependency relationships and showing how much traffic is contributed by upstream services. This would provide a much clearer view of the architecture.
image

Proposal

No response

Open questions

No response

@yurishkuro
Copy link
Member

Sankey works ok when you have strict layering of nodes. It is not the case for microservices dependency graphs. There are playgrounds/notebooks for charting libs where you can try to visualize your existing graph as sankey.

@JellyTony
Copy link

image
Create this kind of application topology diagram.

@Manoramsharma
Copy link

@yurishkuro What kind of feature enhancement is required in this case, Can you please provide some more context on this issue?

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

No branches or pull requests

4 participants