ADR 42: partitioned consumer groups and exclusive consumer #263
Conversation
jnmoyne
force-pushed
the
add-partitioned-consumer-groups
branch
2 times, most recently
from
250d6a0 to
7588f84
Compare
jnmoyne
changed the title
|
@jnmoyne can I close this one but keep the branch around for future reference, we'll refine around the new groups ADR and eventually get back to this but I imagine it would be quite a bit rewrite of this ADR then - big enough to really be new? |
|
Most of this is still valid and only a small part would have to be re-written with the addition of pinned consumers. |
Signed-off-by: Jean-Noël Moyne <[email protected]>
jnmoyne
force-pushed
the
add-partitioned-consumer-groups
branch
from
f940a84 to
7f1a026
Compare
|
Updated to the current initial implementation using the 2.11 features |
|
I'll pick the next available ADR number after an LGTM |
|
Super pumped about this ADR, as this would allow us to move away from sqs with their MessageGroupId & finally centralise on NATs |
|
Note that this is now implemented for Go and has just been released (in Orbit.go): https://github.com/synadia-io/orbit.go/tree/main/partitionedconsumergroups |
3 participants
Consistently hashed partitioned consumer groups (including exclusive client consumption from a durable consumer) for streams.