GeoServer からの移行

Understand the boundary

TasteGeo targets externally observable compatibility, not Java implementation compatibility. Java classes, servlet extensions, and GeoServer plugins do not run inside the Rust server.

• Translate configuration into the supported TasteGeo schema.
• Replace plugin behavior with a verified native capability or keep that traffic on GeoServer.
• Compare HTTP status, headers, content type, and payload semantics.

Inventory

• OGC services and versions
• Workspaces, stores, layers, styles, and security rules
• Community and commercial plugins
• Reverse proxy, TLS, authentication, and monitoring
• Peak traffic and cache behavior

Configuration, datastore, and plugin map

• OGC operations: move only operations backed by a compatibility run for the exact versions in use.
• Datastores: no adapter is implied by its crate or module name; retain each store on GeoServer until an application fixture verifies it.
• Java, community, and commercial plugins: cannot execute inside the Rust process; retain their routes on GeoServer or replace them with a separately verified native capability.
• Styles, security rules, and custom extensions: treat as explicit migration work and mark unverified behavior as currently unsupported.

Parallel operation

Run TasteGeo on a separate origin behind the same reverse proxy. Mirror read-only requests, retain GeoServer as the source of truth, and prevent duplicate write operations.

Traffic cutover

• Freeze configuration changes for the comparison window.
• Run the application-specific compatibility suite.
• Shift a small percentage of read traffic.
• Monitor error rate, latency, cache behavior, and payload differences.
• Increase traffic only when the acceptance criteria remain satisfied.

Rollback

Keep GeoServer configuration and data unchanged during the initial cutover. Rollback must be a reverse-proxy route change, not a data recovery procedure.

• Preserve the previous routing configuration.
• Define an error-rate rollback threshold.
• Stop TasteGeo write paths before restoring GeoServer traffic.
• Record the failed request set as a new compatibility run.

Verification checklist

• All required protocols have a recorded status.
• Every required datastore has an application fixture.
• Authentication and authorization behavior is compared.
• Checksums, signatures, and SBOMs are verified.
• Monitoring and rollback are tested before production traffic.