Reference architectureEvents and IoT
IoT ingestion that tolerates duplicates, disorder, and disconnections
Listeners, idempotency, per-device ordering, dead-letter, replay, and observability without inventing a system protocol.
- IoT
- events
- replay
Knowledge
Architecture explained for better decisions
Guides about production boundaries that matter: failure, state, contracts, persistent data, and recovery. These are reference architectures, not client cases.
Knowledge
Reference architectureGeospatial data
Nominatim: scalable service, persistent data
A stateless application layer around Nominatim with persistent PostgreSQL/PostGIS, caching, and explicit operational limits.
- Nominatim
- PostGIS
- Redis
Reference architectureIntegrations and data
REST/SOAP adapters and PostgreSQL under load
Contracts, retries, idempotency, and domain isolation alongside partitioning, indexes, query plans, bloat, and autovacuum.
- REST
- SOAP
- PostgreSQL
Related cases