Problem Description
When working with pipelines it would be handy to have some sort of visualization for specific messages that are triggered by one another similar to pipes and filters
Proposed Solution
Add another property to the brokerRepository handling pipelines in the frontend.
This property should define a list of topics that will be visualized as a sequence and show that the message indeed came in.
Possible Alternative Approaches
The respective list might also be added to the backend.
Problem with the proposed solution is that lists would be lost on reload of the page.
The backend would be capable of saving the respective lists to the filesystem.
This approach would also enable us to mount predefined pipelines using docker volumes etc.
Problem Description When working with pipelines it would be handy to have some sort of visualization for specific messages that are triggered by one another similar to pipes and filters
Proposed Solution Add another property to the brokerRepository handling pipelines in the frontend. This property should define a list of topics that will be visualized as a sequence and show that the message indeed came in.
Possible Alternative Approaches The respective list might also be added to the backend. Problem with the proposed solution is that lists would be lost on reload of the page. The backend would be capable of saving the respective lists to the filesystem. This approach would also enable us to mount predefined pipelines using docker volumes etc.