Architecture

From Change Event to choropleth.

A Postgres-centric mesh — not another brittle ETL island.

Salesforce Pub/Sub→ CDC subscriber→ pgmq.sf_cdc→ Worker + geocode→ stg / analytics→ tiles · features · Koop · events→ Varnish / NGINX→ GeoLibre SPA

Core principles

  • PostGIS as the mesh — staging, analytics matviews, H3 aggregates, queues.
  • Parallel serving — never force every consumer through one API style.
  • Cache with conscience — TTL plus explicit purge on refresh and writeback.
  • Plugins over monoliths — map UX evolves without rewriting the stack.
  • Cloud portable — containers first; managed services by default.

Security posture

OIDC at the edge for browsers; API keys / bearer JWT for mutations; Salesforce JWT for machine traffic; secrets in cloud vaults — never in the repo.

Pitch it in ten slides

Open the deck →