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.

Sign up for GitHub

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

Jump to bottom

YAGNI architecture stuff #27

Open
attentive opened this issue Aug 29, 2016 · 5 comments
Open

YAGNI architecture stuff #27

attentive opened this issue Aug 29, 2016 · 5 comments

Comments

@attentive
Copy link
Contributor

A proper solution to the problem of a public-facing map georeferencing tool would use a messaging architecture for the batch processing backend (the warping part) and allow for the possibility of a cluster of processing hosts.
@attentive
Copy link
Contributor Author

Celery might be the go for decoupling long-running processes (warps, gdaladdo etc) http://docs.celeryproject.org/en/latest/getting-started/first-steps-with-celery.html

@attentive
Copy link
Contributor Author

If we built a Flask app, could use Flask-GraphQL for the application (not API) aspects https://github.com/graphql-python/flask-graphql

@attentive
Copy link
Contributor Author

https://github.com/graphql-python/graphene also seems useful …

@attentive
Copy link
Contributor Author

See also https://github.com/graphql-python/graphene/tree/master/examples/flask_sqlalchemy

@keithamoss
Copy link
Contributor

Twisted Klein may work as well and let us stay closer to a Flasky experience.

@attentive Is that going to tick the boxes from your POV?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@attentive @keithamoss