On a large mongoDB I have 2 different use-cases for reading and 2 different types for write/update.
- read 1: find by index -> no question on this. this works like a charm - as long as the index fits in the memory/ram.
- read 2: read line by line, like a batch script which is reading a log-file one by one.
- write 1: insert - append a new dataset or document.
- write 2: update data, directly addresses or found by index.
Now I wonder if mongoDB is able to "priorize" different write-tasks. I have one collection which does not require the data to be written and available instantly in "real-time". It's enough to use a slow queque and process these writing tasks without hurry. However, there are also write statements that should be processed asap and be available with a minimum delay (if any).
Does mongoDB allow me to differ between high (asap) and low prio (queque) writing/updating?