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
But instead of having the application in the center, it will be a single channel with external applications around it, showing who receives from it and who sends to it.
The text was updated successfully, but these errors were encountered:
Yeah, I'd say this is one of the most powerful use cases. This would help people make sense of their EDA.
Most of the time, the biggest concern people find about EDA and why they land on AsyncAPI, is that they have no idea who's consuming from or producing to a channel. They fear that if they change something on the message that's being published there, a consumer will break. And the result is that they end up creating a new channel so they don't break anything. This bloats their system with lots of unnecessarily duplicated (or almost duplicated) channels, making it more expensive, harder to maintain, and more energy-consuming.
This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.
There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.
Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.
Reason/Context
So far all the views have been revolving around applications and how they interact with the world through channels.
But sometimes you wish to focus on a single channel and who interacts with that.
Therefore I am proposing we add a new view, similar to the
ApplicationFocusView
as you can see here: https://asyncapi.github.io/EDAVisualiser/social-media/backendBut instead of having the application in the center, it will be a single channel with external applications around it, showing who receives from it and who sends to it.
The text was updated successfully, but these errors were encountered: