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
Currently EventBus based on Kafka looks like a black box. And in order to build robust system we need more context.
Describe the solution you'd like
Need more info from maintainers about:
How each topic event, trigger, action is used by Argo Events
If we have messages with different payload, should we create several EventBus or one EventBus is enough
Recommendations about what partitions we need to set for topics if we expect high amount of messages. Should we set number of partitions for event, trigger, action topics or only for events.
Also whatever you think will be useful to understand on how we can work with it.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently from description here https://argoproj.github.io/argo-events/eventbus/kafka/#topics it's hard to understand on why each topic is needed and how Argo Events will use it.
Currently
EventBus
based on Kafka looks like a black box. And in order to build robust system we need more context.Describe the solution you'd like
Need more info from maintainers about:
event
,trigger
,action
is used by Argo EventsEventBus
or oneEventBus
is enoughevent
,trigger
,action
topics or only forevents
.Also whatever you think will be useful to understand on how we can work with it.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: