Architecture decisions¶
Every structuring decision is recorded in an ADR (Architecture Decision Record), based on the template.
| ADR | Title | Status |
|---|---|---|
| 0001 | Documentation tooling and structure | accepted |
| 0002 | GeoServer workspace organization | proposed |
| 0003 | Parameter identification and granule naming | accepted |
| 0004 | Database initialization by a standalone Job and one JNDI resource per source | accepted |
| 0005 | Official image, plugins at build time, ephemeral data dir, security/ in the database |
accepted |
| 0006 | Reproducible configuration via a Java plugin, not via REST | accepted |
| 0007 | Provisioning of plugins and artifacts | proposed |
| 0008 | Hazelcast clustering via Kubernetes DNS discovery; UI sessions | accepted |
| 0009 | S3 object storage for the tile cache and the rasters (COG) | accepted |
| 0010 | Ingestion: COG on S3, PostGIS index, views, no notification | accepted |
| 0011 | Observations: TimescaleDB hypertable, one view per layer, canonical values | accepted |
| 0012 | Basemaps: hosted reference data first, cascaded WMS as a complement | accepted |
| 0013 | Sparse upper-air interpolation: model first guess + observed corrections | accepted |