You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Proposal
No response
Open questions
No response
The text was updated successfully, but these errors were encountered:
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.
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.
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.
Proposal
No response
Open questions
No response
The text was updated successfully, but these errors were encountered: