Historical Atlas / API service
DRAFT SPECTry the sandbox →
BACKEND / DEVELOPER REFERENCE

One service.
Defined boundaries.

REST + JSON
SESSION AUTH
GEOGRAPHIC DATA

A location directory built around a Spring Boot monolith.
Explore its API responsibilities without pretending a backend is running.

LOCAL SIMULATOR Requests below execute JavaScript in this page. No server, database, Keycloak or generated OpenAPI document is connected.
APPLICATIONSpring BootJava · Maven · One deployable
STRUCTUREModulithTop-level package APIs · No cycles
PERSISTENCEPostGISPostgreSQL · WGS 84 geography
IDENTITYKeycloakBackend session · Role-based access

INTERACTIVE REFERENCE

Request sandbox

MEMORY ONLY / RELOAD TO RESET

Example location payloads are illustrative: the linked location schema is not included in this input. This is not a generated or authoritative API contract.

REQUEST COMPOSER 01

No fetch calls. No latency measurements.
Simulated response and IDs only.

SIMULATED RESPONSE READY
Execute a request to inspect its expected behavior.
{
  "notice": "Illustrative JSON, not a live API",
  "locationCount": 2
}
IN-MEMORY LOCATIONS2
LOCAL AUDIT EXAMPLES IDs only · no entity content
No simulated changes yet.

APPLICATION MODULES

A monolith, not microservices.

org.avarc.server

PERSISTENCE CONTRACT

Coordinates in. Geography derived.

PostgreSQL + PostGIS

The application reads and writes latitude and longitude columns. A generated geography point uses WGS 84; longitude is X, latitude is Y.

schema: avarc
identity: UUID
position: geography(Point, 4326)
discriminator: kind

Flyway → versioned migrations
Hibernate → validate mapping
Testcontainers → PostGIS tests

Coordinate preview

Pure math / no spatial query is executed.

POINT(-0.1278 51.5074) · SRID 4326

Flyway manages only the avarc schema, keeping PostGIS-owned schemas separate. Runtime database address/user come from environment configuration; the password is a file secret. No configuration or secret is read here.

OPERATIONAL BOUNDARIES

Expose deliberately. Observe carefully.

01 / DOCUMENTATION

Dev & stage only.

Generated springdoc OpenAPI at /api/docs/openapi.json and Swagger UI at /api/docs are readable without login only when enabled in those profiles. Production serves neither. Actual operations still require a session; changing requests require CSRF proof.

02 / MANAGEMENT

A separate port.

Actuator defaults to 9091 on the metrics network. Application-port /actuator returns 404. Health/readiness and Prometheus are default; dev/stage expose all management endpoints. Ingress routes management only in dev/stage per this backend source.

03 / TELEMETRY

IDs, not content.

Structured JSON lines carry request IDs and opaque Keycloak subjects. Micrometer reports route/status, connection-pool and JVM metrics. Audit records location/tag changes with action, entity type and ID — no content.

Build, formatting & dependency policy

Maven builds the Java service. Open Java Format uses a single 120-character style, rewrites in normal process-sources and checks with CI or -Pformat-check. Formatter/POM versions are managed explicitly. Patched Boot-managed libraries may use BOM property overrides until Boot catches up. This frontend neither runs these tools nor claims their checks passed.