feat: jetstream partitioned consumer groups #20
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oliverlambson
changed the title
oliverlambson
force-pushed
the
feat/jetstreampcg
branch
4 times, most recently
from
0be47f7 to
ddc6342
Compare
oliverlambson
force-pushed
the
feat/jetstreampcg
branch
from
ddc6342 to
5128b87
Compare
oliverlambson
force-pushed
the
feat/jetstreampcg
branch
from
5128b87 to
fb616f7
Compare
oliverlambson
force-pushed
the
feat/jetstreampcg
branch
from
fb616f7 to
72c44d9
Compare
oliverlambson
force-pushed
the
feat/jetstreampcg
branch
from
72c44d9 to
1a25e59
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Important
needs support for priority groups in nats-py, see nats-io/nats.py#784
implemented in nats-io/nats.py#786 – this PR depends on that branch
port of partitioned consumer groups from orbit.go
pull consumer priority groups were added in ADR-42, they allow for partitioning of consumers into "consumer groups" with pinning to ensure ordered consumption within a partition without having to consume the entire stream sequentially.
e.g. in event sourcing you normally want to consume events sequentially within an aggregate, but can safely process multiple aggregates concurrently
todo: