I’ve been wondering. I’m dealing with a project where an external API is responsible for all updates. I’m unable to use the oplog, so Meteor falls back to using the polling observer. Basically:
Method -> API Call -> DB update -> Poll (on interval) -> Publish -> client update
The problem is that now it might take up to 10 seconds for my update / remove to appear on the clientside. Which is… not great. I’ve been looking into the latency compensation, updating the clientside only, but this change is ofcourse directly undone by the Meteor serverside only to be done again when the update from the external API also reaches the server…
Another option would be to update the server’s minimongo collection and push the changes to each client, but without persisting the change allowing to let the API take all the time it needs to to the update on the database.
Anyone that has been dealing with this scenario that can help me out?