Thanks for wanting to share this; the best way is to create a new wiki page on the MapServer wiki (https://github.com/mapserver/mapserver/wiki) and there you can outline all of your infrastructure tricks, then you can come back here and paste your link to your MapServer magic :)

Thanks again,

-jeff



On 2019-08-29 4:55 AM, Wouter Visscher wrote:
Hi all,

I'm working for the Dutch NSDI www.pdok.nl <http://www.pdok.nl/>, where we have around 200 datasets ranging from the larger ones like address, buildings, cadastral parcels and smaller ones like hikingtrails, natura2000, and so on. Our platform is used a lot in the Netherlands, both by the public and private sector, last year we hit 12 billion requests. To be able to handle that amount of traffic we are now in a transition, moving from a private cloud solution to the public cloud. With this change, we needed to refactor our software stack.

Through some experimentation, and on the job 'training' we are now running the following setup: A minio.io <http://minio.io/> (S3) blobstore, containing geopackages with the vector data and geotiff's for the rasters. Our mapserver configurations connects to these files with /vsicurl/. Our mapservers are in docker containers that we run on kubernetes. With this setup we are able to create a scalable infrastructure from which we can push WMS/WFS/WMTS interfaces to the web.

If people are interested in how we deploy our mapserver software stacks I would be happy to share our k8s deployment setup/configurations.

Wouter Visscher

_______________________________________________
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users



--
Jeff McKenna
MapServer Consulting and Training Services
https://gatewaygeomatics.com/
_______________________________________________
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Reply via email to