0

I try to study the topic of Spring Reactive and MongoDB change streams.

And i run with quite a lot of change streams as i develop my application (up to 10 so far - but still) - so far so good, but i believe when being used by multiple users it can affect memory usage/performance or anything.

Can you, please, advise me on the following items:

  1. I have websockets in the set-up and i am assuming that if the WS session is completed - then the corresponding change stream is garbage collected - is that right?

  2. Is there any particular recommended way to centrally manage change streams for different collections?

  3. And what could be maximum and preferred number for change streams in general?

Mike
  • 63
  • 1
  • 7

1 Answers1

1

I would recommend to create as few change streams as possible, because they can cause a lot of query-load on your database.

I don't know your specific use case, but I would recommend a maximum of one change stream per collection.

All of your subscribers should subscribe to the same change stream.

If subscribers require different subsets of changes, it would be their responsibility to filter the stream to their specific needs.

Erunafailaro
  • 1,835
  • 16
  • 21
  • 1
    I also wanted to double-check - is it a good way to define those changeStream objects as Singleton beans then? – Mike Aug 19 '21 at 19:35
  • Yes, that would be my recommendation. Change stream should be singletons, if you ask me. – Erunafailaro Aug 19 '21 at 21:27