Continuation of ResonantGeoData/ResonantGeoData#285
Have two queues: one for running fast, high-priority ETL routines (e.g. populate_raster_entry) and one for running slow, low-priority ETL routines (e.g. populate_raster_footprint)
Note changes in ResonantGeoData/ResonantGeoData#294
On the Heroku deployment, we should also set it up so that we can easily spin up a second worker and handle each queue on separate workers (for now, we do not need this)
Continuation of ResonantGeoData/ResonantGeoData#285
Have two queues: one for running fast, high-priority ETL routines (e.g. populate_raster_entry) and one for running slow, low-priority ETL routines (e.g. populate_raster_footprint)
Note changes in ResonantGeoData/ResonantGeoData#294
On the Heroku deployment, we should also set it up so that we can easily spin up a second worker and handle each queue on separate workers (for now, we do not need this)
See ResonantGeoData/ResonantGeoData#326