Prototype a multiprocessing solution using a separate blobs server
Because we will not modify the platform now, we want an intermediate solution for the multiprocessing problem that will allow for usage with the current server and will also be usable when we migrate to platform-based routing.
This is the proposed structure for theis solution:
- business as usual, if not configured (everything runs in the same process).
- if soledad-blobs-detached-server configured, then it's responsibility of sysadmin to run
soledad-blobs-server
.- if
/sync
, do as usual. - if
/blobs
or/incoming
or/stream
, delegate request to localsoledad-blobs-server
port.
- if
Obs: soledad-blobs-server
is a new entrypoint, very lightweight (no weird dependencies, just Twisted). It is a router that spawns multi process and worries about task coordination.
Edited by drebs