NodeJS Message router implementation

Open
#339 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, node.js
Domain
backend, distributed-systems

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.

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.
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.

Dominant language
C++
Stars
164
Forks
99
Avg merge
5d 18h
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/pulsar-client-node

All issues in apache/pulsar-client-node

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.