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 motivation is to enable organizations to define their path & metadata semantics, yet to have a typed representation of this semantic. In order to keeping a strict convention within multiple teams within the organization.
This spec deals with two kinds of semantics:
Stream name: dictate the stream name (for example environment, partition, shard)
Deployment context: contextual information like which cluster/namespace the event created on and which one is handling the current execution (this one is related to a scenario when two different contexts synchronize their events)
What will be affected by this feature
Builders
Metadata
Channels
The text was updated successfully, but these errors were encountered:
The motivation is to enable organizations to define their path & metadata semantics, yet to have a typed representation of this semantic. In order to keeping a strict convention within multiple teams within the organization.
This spec deals with two kinds of semantics:
What will be affected by this feature
The text was updated successfully, but these errors were encountered: