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

Add event processing abstractions #13

Open
tobyclemson opened this issue Dec 5, 2024 · 1 comment
Open

Add event processing abstractions #13

tobyclemson opened this issue Dec 5, 2024 · 1 comment

Comments

@tobyclemson
Copy link
Member

In order to process streams asynchronously, it would be nice to have some sort of event processing abstractions.

Examples of what would be nice:

  • Consumers at the log, category or even stream level that subscribe to the store to be invoked when relevant events are written to the store
  • Producers allowing new events to be written into the store asynchronously
  • Some form of leader election to allow ownership of log, category or stream processing to be managed via some sort of competing consumer model
  • Timers allowing scheduling and triggering of processing activity
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

2 participants
@tobyclemson and others