The FileWorker architecture is based on workers / instances pulling tasks as their resources allow it.
Reasons:

1. When scaling Meteor we will run on multiple instances using oplog to keep data in sync - but storing uploaded files in TempStore should be available to all instances (we can loose instances in some arcs)
2. The concept of transform streams allows for heavy analyze of data / files - so we would like to be able to isolate those not crashing the main servers

We could scale by having multiple Meteor instances and use gridFS for TempStore (uploaded files)
Tasks will be retrieved by using a request pattern via db - ensuring one worker pr. task.

• Rework the cfs-worker implement better throttling