Assume a meteor server synchronously inserts 100 docs into collection A, then inserts 100 docs into collection B, and then inserts 1 doc into collection C.
Consider a client that is subscribed to all of these collections without restriction. Are there any insert ordering guarantees for the subscribed client? That is, would all A inserts be made at the client before any B inserts, thus matching the server insert order? Does it depend on the number of inserts to A?
This question stems from a stylized use of the above pattern and attempt to use the C insert to signal that both A and B have been fully updated. Unfortunately, it appears that only some of the A and B inserts are made prior to the C insert and I’m trying to understand how Meteor and DDP orders collection inserts for one or more collections.
Any insight is appreciated.