Hi, we are working on a solution on AWS and are using MongoDB Atlas as DB.
Right now we are using the MongoDB Atlas Shared cluster.
We require a change stream for some of our collections, so we can execute side-effects and update other transitive collections when specific conditions are met. In AWS we are already using Event Bridge and i thought its a good use case for using the MongoDB Atlas Trigger into AWS Event Bridge.
So far so good. Though when we had implemented it, we saw that the MongoDB Atlas Trigger has a hard time with catching up our burst load. There are burst loads, when we are updating ~50k item in one collection. With ordering enabled the trigger only delivers 3-4 items per second.
Without the ordering it manages to handle the burst, though when handling updates of a document, the order is important i guess.
So my question is, is there anything else we can do? Should we move to another concept to achieve our change stream? I am glad for every advice!