Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Where should the data processing actually run? #22

Open
mccalluc opened this issue Jan 17, 2020 · 0 comments
Open

Where should the data processing actually run? #22

mccalluc opened this issue Jan 17, 2020 · 0 comments
Labels
question Further information is requested

Comments

@mccalluc
Copy link
Collaborator

Having a webapplication spawn a subprocess, much less a docker container, is a bad idea. Even apart from security concerns, there's a mismatch between the needs of the webserver (minimal! except for storage... see #19 and #20.) and the needs of the processing (huge, above 10G RAM, at least.)

This might be appropriate for AWS Lambda, if the jobs can run quickly enough. Google or Azure might have their own offerings in this space.

Different compute platforms would support different storage possibilities.

@mccalluc mccalluc added the question Further information is requested label Jan 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant