Ergonomic facade over the generated event-bus binding.
One publisher, many subscribers, inside a single process. It is how the parts
of a gateway talk to each other without knowing about each other, so a
sampler can announce a reading and whatever cares about readings picks it up.
A subscriber only sees events published after it existed, so subscribe before
publishing anything it needs to see. An EventBus endpoint publishes and
receives; an EventPublisher only publishes, so a part that announces and
never reads holds one of those.
Ergonomic facade over the generated event-bus binding.
One publisher, many subscribers, inside a single process. It is how the parts of a gateway talk to each other without knowing about each other, so a sampler can announce a reading and whatever cares about readings picks it up.
A subscriber only sees events published after it existed, so subscribe before publishing anything it needs to see. An
EventBusendpoint publishes and receives; anEventPublisheronly publishes, so a part that announces and never reads holds one of those.