Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open Closed key & metadata convention #42

Open
3 tasks
Tracked by #12
bnayae opened this issue Sep 22, 2022 · 0 comments
Open
3 tasks
Tracked by #12

Open Closed key & metadata convention #42

bnayae opened this issue Sep 22, 2022 · 0 comments

Comments

@bnayae
Copy link
Contributor

bnayae commented Sep 22, 2022

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
@bnayae bnayae mentioned this issue Sep 22, 2022
51 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant