HISTORICAL LOCATION DIRECTORY
A map of the
system behind the map.
Trace the route from a browser to historical data. Explore trust boundaries, service responsibilities, and what comes after the MVP.
avarc-server · SOLID: MVP / DOTTED: POST-MVPAlloy → LokiPrometheus → service metricsGrafana → Loki + Prometheus
Browser → ingress / HTTPS; pages → Next.js; /api → Spring Boot
Login / logout /auth/realms/avarc → Keycloak; backend exchanges code and retrieves signing keys
Persistence Backend → JPA / Flyway → PostgreSQL + PostGIS; Keycloak → its own database
Database tool Optional dev/stage access → database, read-only
Log pipeline Alloy collects container log files → Loki → Grafana
Metrics pipeline Prometheus scrapes backend management ports, Keycloak and ingress → Grafana
Public map / post-MVP Anonymous browser → HTTPS ingress → map server → public database data
Assistant / post-MVP AI MCP client → ingress → MCP server → backend API; token validation → Keycloak