NATS client-server architecture problem

[michallm]

Hello,

I'm having trouble designing consumers on multiple target devices.

I have one main nats-server (jetstream) that connects multiple devices. One stream is created on the server, let's assume the name ORDERS.

Each device is to receive events from the server. Eg device1 will get orders.created event and device2 too.

Should I create a separate consumer for each topic? For 5 themes, it will be 5 consumers on the server. For two devices, it will be 10 consumers.

Is it possible to subscribe to different topics with the same consumer and process them separately?

[derekcollison]

We normally recommend using a single stream and mux all subjects into that and have a separate filtered consumer for each set of messages you want to process independently..

[michallm]

if I have two devices, each of them has the OrderCreated consumer, but with different queue groups (dev1, dev2), both will get an event? I'm right?

[derekcollison]

Delivery of messages is bound by the consumer state, so if you have two consumers that have same starting stream sequence then those messages will be delivered to each.

[michallm]

Ok. Thank you