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

Event stream partitioning. #98

Open
jmalloc opened this issue Jun 11, 2023 · 1 comment
Open

Event stream partitioning. #98

jmalloc opened this issue Jun 11, 2023 · 1 comment

Comments

@jmalloc
Copy link
Member

jmalloc commented Jun 11, 2023

The current event stream API does not allow specification of a stream within an application. It is assumed that every application has exactly one stream (as is the case with Verity).

We need to support multiple streams per application. This could be done by adding an additional piece of information to the API - a "partition ID" or "stream ID".

Another approach would be to simply rename "application ID" to "stream ID" within the consume request. Verity would simply use the application as the stream ID, whereas Veracity would be free to expose multiple streams with other IDs.

Regardless of the approach taken, the event stream API will need a way to enumerate the available streams.

There may also be a requirement to include "site" information in the API.

@jmalloc jmalloc moved this to Accepted in Dogma General Availability Jun 11, 2023
@jmalloc jmalloc moved this from Accepted to In Progress in Dogma General Availability Apr 3, 2024
@jmalloc
Copy link
Member Author

jmalloc commented Apr 3, 2024

A new gRPC API has been added to enginekit. No site related functionality has been added (and may not be necessary in this API, not sure yet).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

1 participant