ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Shared subscriptions in Pulsar destroy per-key ordering by round-robining messages, while failover subscriptions refuse to scale. Key_Shared restores ordering per key by hashing keys onto consumers—here is how it works, where it breaks, and how to verify it.
Pulsar's Key_Shared subscription preserves per-key ordering while scaling consumers horizontally. Here's how it routes messages, a working example, and the hot-key and rebalancing trade-offs to design around.
Pulsar's Key_Shared subscription keeps every message key in order while the consumer group scales. How the hash routing works, what hot keys and rebalances cost, and how to verify it on your cluster.
pulsar