This message was deleted.

If your goal is to have every consumer receive their own copy of each message on a topic, then each consumer should have their own unique Exclusive subscription regardless of the client library used (Websocket or otherwise)

So there isn't a way to broadcast the most recent message to 3 instances of a nodejs websocket running in k8s? The exclusive subscription type doesnt seem to scale horizontally, only vertically. I found this post trying to do a similar operation https://stackoverflow.com/questions/60606241/how-to-do-broadcast-in-pulsar We only care about scaling, low latency, and having the same data displayed across all instances on angular frontend...

The topic is the entity holding the messages. Subscription is the entity through which you read from a topic. It’s the one saving which messages you have acknowledged or not. If each websocket needs to have read the topic messages, independent of other web-sockets, then each should use its own subscription.