Open
Description
We're seeing lots of latency spikes with Cloud Files, which is creating headaches with preparers that need to sequentially submit hundreds of documents. With latency spikes approaching one minute (that's an hour in internet time), it would make sense to treat Cloud Files writes as an asynchronous task that happens in the background.
Something like resque would be a natural choice for this, but would require that the task queue/runner be a separate container in the pod (Ruby). We could add the task queue/runner directly to the content service, but would need to use one of the Node.js ports of resque or another similar task runner.