What is best approach to polling a MongoDB database looking for changes

Asked Jun 16 '22 at 08:04

Active Jun 16 '22 at 08:07

Viewed 628 times

I have two microservices (ServiceA and ServiceB).

ServiceA inserts records into a MongoDB database.
ServiceB check in MongoDB if there are new records and does some work with theses new records.

ServiceB is a backgroundservice, in ExecuteAsync method, I query MongoDB to check new records every second.

Is it a good approach to query the database every second? (Is it not too resource intensive? It's a select with where condition)

Otherwise, I was thinking of using RabbitMQ:

ServiceA inserts records in MongoDB database and pushes message (Id of record) to RabbitMQ.
ServiceB consumes RabbitMQ's message and does work.

edited Jun 16 '22 at 08:07

Mark Rotteveel

asked Jun 16 '22 at 08:04

Julien Martin

Possibly of [interest](https://stackoverflow.com/questions/53644013/push-notification-service-in-database-triggers-mongodb-stitch) – TaW Jun 16 '22 at 08:11
1

I'd opt for the message queue, especially if the infrastructure is already in place. – Markus Jun 16 '22 at 08:44
Yes the infrastructure is already in place – Julien Martin Jun 16 '22 at 08:52

0 Answers0