We are currently facing challenges with scaling as we add more databases in our application. Specifically, we use MongoDB Triggers for monitoring changes, but we understand that both Triggers and manual watch streams rely on the same underlying change stream mechanism.
- Triggers and Change Stream Capacity: From my understanding of Atlas Triggers Limitations, the limitations apply to all change streams, whether managed via Triggers or manually through the
watchAPI. If this is correct, is there any way to increase capacity for triggers/change streams to monitor more collections or databases? - Moving to Custom Streams: Would implementing a custom change stream solution (using the
watchAPI on our own servers) allow us to bypass some of these limitations? For instance, would it enable us to monitor more collections/databases compared to using Triggers?
We are looking for the best approach to scale monitoring for multiple databases while staying performant and cost-effective. Any insights or recommendations would be greatly appreciated!
Thank you!