2026-06-29 –, A02
You assumed you'd spend your time creating GIS layers, but the computer said no. Now you're spending your evenings reading logs. There's got to be a better way?
Welcome to the story about how we rebuilt our 50 requests/s GeoServer setup, and what we learned along the way. We'll take a look from an IT/Operations point of view, and describe how we automated GeoServer updates and built a cluster. What worked for us and what did not?
GeoServer
Assign a number between 1 and 4 indicating the level of technical complexity of your contribution.: 2: some technical/thematic skills required Select at least one general theme that best defines your proposal: Data collection, data sharing, big data, data exploitation platforms Under which license do you make your contribution available? The conference contribution comprises the abstract, the text contribution for the conference proceedings, the presentation materials as well as the video recording and live transmission of the presentation: CC BY-SA
A software engineer specializing in stable high performance software. Currently working at Flanders Marine Institute ( www.vliz.be ) analyzing sensor data from the the Scheldt River. Interested in a wide area of technology, from Python to Rust, from databases to front end, from HPC to GIS.
Data scientist building Shiny applications powered by GeoServer, with prior experience in QGIS and remote sensing for disease vector modelling. For the past year at Flanders Marine Institute, she has focused on translating geospatial services into practical data tools.