Replies: 5 comments
-
This is one of the main values of buckets for me, to organize events. To make it easier for users starting in some area to see the events they should care about or use. This doesn't, however, actually need to be reflected in the event type, we could have a "flat list" of events from an event type perspective, and deal with grouping in the documentation. I don't have an opinion on the use of tags, as I don't understand the use case of filtering events by group rather than by specific type. Is it for when "we only want to copy events of this specific group to this public message bus"? What if some old event is suddenly update to include a new tag? Seems risky. |
Beta Was this translation helpful? Give feedback.
-
In |
Beta Was this translation helpful? Give feedback.
-
Related issues: #45 |
Beta Was this translation helpful? Give feedback.
-
Having buckets would limit in which stage a certain task type is used. Testing - as an example - is used in CI, CD or progressive delivery or even production for chaos testing. Currently the buckets are heavily tied to lifecycle stages. |
Beta Was this translation helpful? Give feedback.
-
I agree with @AloisReitbauer and would prefer not to have the bucket in the events themselves. Tags is a much better way if we want some kind of grouping. |
Beta Was this translation helpful? Give feedback.
-
We organised our protocol events in four buckets (or phases):
These buckets are a good way to organise our documentation and perhaps protocol spec.
We should clarify what the bucket mean from a protocol and implementor point of view.
The initial proposal @salaboy was to include the bucket name in the event name.
Advantages:
Disadvantages:
An alternative solution could be to leave the bucket name outside of the event type, which would gives us more flexibility in changing the buckets without impacting the protocol directly.
We could allow for (optional?) multi-value custom headers to specify categories. This would allow to:
For instance an event could be in the
ci
bucket and related totesting
, and that could be mapped to two tags.Perhaps in future we could decide that
testing
is a bucket of its own.Beta Was this translation helpful? Give feedback.
All reactions