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
The Allowed Publishers, ability to Request to Publish and the Linking of events are dictated by the topic descriptor. This is what we call event topology given it dictates how the event tree is structured.
The event descriptor remains unchanged with the exception of two distinct fields in its metadata which is author and publisher.
This also introduces a new kind of RPC which is REQUEST_TO_PUBLISH essentially sending an event without a publisher, looking for someone willing to publish it.
Consequences
The essential idea is to add support for multiple scenarios where we want to control who's allowed to publish and how are the events linked.
Examples:
If we wanted to have order guarantee in our event tree (essentially creating a chain of linked events) we could have a topic with only its author as an allowed publisher, that would allow requests to publish and where the event linking is done based on the last seen event.
If we wanted to leave it up to application how the events are to be linked, we could allow custom event linking, giving the ability to set a custom parent to the event at the time of publish.
The text was updated successfully, but these errors were encountered:
After discussion with @luisveiga some changes were performed to the specification of Pulsarcast. These changes have been implemented in https://github.com/JGAntunes/js-pulsarcast already.
Changes
The Allowed Publishers, ability to Request to Publish and the Linking of events are dictated by the topic descriptor. This is what we call event topology given it dictates how the event tree is structured.
The new Topic Descriptor:
The event descriptor remains unchanged with the exception of two distinct fields in its metadata which is
author
andpublisher
.This also introduces a new kind of RPC which is
REQUEST_TO_PUBLISH
essentially sending an event without apublisher
, looking for someone willing to publish it.Consequences
The essential idea is to add support for multiple scenarios where we want to control who's allowed to publish and how are the events linked.
Examples:
If we wanted to have order guarantee in our event tree (essentially creating a chain of linked events) we could have a topic with only its author as an allowed publisher, that would allow requests to publish and where the event linking is done based on the last seen event.
If we wanted to leave it up to application how the events are to be linked, we could allow custom event linking, giving the ability to set a custom
parent
to the event at the time of publish.The text was updated successfully, but these errors were encountered: