geogeeks-au / maps-for-lost-towns

Georeferencing historic maps through crowdsourcing
4 stars 1 forks source link

YAGNI architecture stuff #27

Open attentive opened 8 years ago

attentive commented 8 years ago

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 commented 8 years ago

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 commented 8 years ago

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

attentive commented 8 years ago

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

attentive commented 8 years ago

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

keithamoss commented 7 years ago

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?