I have a web service that serves two purposes.
- On a weekly basis, it syncs records from the GIS DB to a workorder management system's database.
- On a continual basis, it serves up the records to a web map in the work order management system.
Here is a summary of purpose #1 and purpose #2:
(There are 40+ spatial views/layers in the web service that are based on spatial tables.)
The current multi-purpose web service works fine for #1 (db sync), but it's too slow for #2 (the web map).
What are my options for managing this multi-purpose web service?
- Split the single web service into separate web services. Each service would be catered to a specific purpose.
- Or precompute the layers in the web services by using materialized views or a python job (to export the views to static tables). This would solve the performance issues in 2A and 2B.
- Or something else?