Overview & Architecture

GeoServer Core is the central processing engine that handles spatial data storage, styling, rendering, and secure delivery. It operates as a lightweight, high-performance service that can be deployed on-premise, in containers, or across managed cloud infrastructure.

The architecture follows a modular plugin system, allowing administrators to enable only the required data stores, output formats, and security modules. Request routing is optimized for concurrent WMS/WFS/WCS operations with built-in tile caching and stateless rendering pipelines.

Core Capabilities

📦

Multi-Format Storage

Native support for PostGIS, GeoPackage, Shapefile, GeoTIFF, and vector tiles. Hot-pluggable data store architecture.

🎨

SLD/SeCSS Styling

Full OGC SLD 1.1/1.2 compliance with CSS-style authoring, dynamic label placement, and symbol libraries.

🔐

Layer Security

Row-level security, attribute filtering, and role-based access control integrated with LDAP, OAuth2, and SAML.

⚡

Tile & Cache Engine

Internal GeoWebCache integration, async tile generation, and automatic cache invalidation on data updates.

📡

OGC Protocol Suite

WMS 1.3.0, WFS 2.0, WCS 2.1, CSW, and OAPIF (OGC API Features) compliant endpoints out of the box.

📊

Observability

Prometheus metrics, structured JSON logging, distributed tracing headers, and audit trail exports.

Technical Specifications

Parameter Value / Standard Notes
Runtime Java 17 / 21 (LTS) Tomcat 10.1 or Jetty 12 recommended
Rendering Engine JAI-ImageIO + Mapnik Bridge Hardware-accelerated where available
Max Concurrent Requests Unlimited (CPU-bound) Auto-tuned thread pools per data store
Output Formats GeoTIFF, PNG, JPEG, SVG, PDF, Vector Tiles (MVT), GeoJSON Plugin-based format registry
Coordinate Reference Systems PROJ 9.x, EPSG Registry On-the-fly reprojection supported
Deployment Docker, Kubernetes, WAR, Standalone Helm charts & Terraform modules available

Data Integration Workflow

GeoServer Core ingests spatial data through a unified catalog service. Data sources are registered as JDBC connections, file watchers, or REST API streams. Once cataloged, layers are exposed immediately with automatic feature type inference and bounding box calculation.

For enterprise pipelines, the core engine supports:

  • Kafka/ZeroMQ listeners for real-time feature updates
  • S3/GCS adapters for serverless raster storage
  • Schema versioning with automatic migration hooks
  • Feature locking for concurrent editing via WFS-T

Configuration Example

Below is a minimal XML configuration for a PostGIS data store with row-level security enabled:

<!-- geoserver-data.xml --> <dataStore name="production_gis"> <connection type="PostgreSQL"> <host>db.internal</host> <port>5432</port> <database>spatial_prod</database> <schema>gis</schema> <pool max=20 idle=5/> </connection> <security> <filter type="row" clause="tenant_id = current_user_tenant()"/> <cache>enabled</cache> </security> </dataStore>

Release Notes (v3.2.0)

Release Date: March 2025 | Target: Enterprise & Cloud Deployments

  • Improved WMTS endpoint response time by 40% via lazy tile assembly
  • Added native support for OGC API - Processes (Draft 1.0)
  • Resolved memory leaks in large GeoTIFF pyramid generation
  • Updated PROJ database to v1.11 for latest datum shifts
  • Enhanced REST admin API with batch deployment capabilities