apache / apache/pulsar-client-node
NodeJS Message router implementation
- Dominant language
- C++
- Stars
- 164
- Forks
- 98
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
My goal is to ensure a consumer will always receive key associated messages.
But from my tests, on adding/removing consumers there are cases where Pulsar will do a rebalance.
So I think my best shot is to publish to a specific partition and subscribe to this specific partition with my customer.
So what I would do is implement the Message Router interface [as explained here](https://pulsar.apache.org/docs/3.0.x/concepts-messaging/#routing-modes).
But I could not make it in the Node.js client, as it does not seem to exist.
Will that be implemented in the future ?
Let me know if I'm mistaking or if it's unclear, as I'm pretty new to Apache Pulsar.
Thanks for reading.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the linked Pulsar routing modes documentation, then inspect the Node.js client for its producer APIs and any existing Message Router interface or routing tests. Done means the client exposes the requested message-router behavior and supports routing keyed messages to the intended partition without unwanted rebalancing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100