Technical Specifications
Engineered for perpetual records
Microservices architecture purpose-built for cemetery operations: GIS-mapped plot inventory, FBCSA-compliant rights management, real-time scheduling, perpetual care fund tracking, and genealogical portal — all on an event-sourced, immutable-record platform.
99.9%
Uptime SLA
5,000+
Concurrent Users
<200ms
API Response
9
Platform Modules
Architecture Overview
Civic Cemetery runs on a containerized microservices architecture purpose-built for bereavement services. Each domain — plot registry, rights management, interment scheduling, perpetual care fund accounting, and genealogical records — operates as an independently deployable service with its own data store and API. Services communicate via event-driven messaging to maintain consistency across burial records, financial transactions, and public-facing memorial portals.
Platform Modules
Core Services
Independently deployable microservices with dedicated data stores and APIs.
Total Modules
9
Protocol
REST / gRPC
Bus
Async Events
Container
Kubernetes
Database
PostgreSQL 16
Specifications
Technical Details
Browse specifications by category. All values reflect current production configuration.
Plot Search
< 200ms
Map Rendering
< 1.5s
Rights Processing
< 500ms
Report Generation
< 3s
Uptime
99.9% Availability SLA
Enterprise-grade availability with redundancy across Canadian data centres.
99.953%
30-Day Avg
1
Incidents
3× DC
Redundancy
< 15min
Recovery
30-Day Uptime History
All Systems Operational
Deployment
Flexible Deployment Options
Source code licence with flexible deployment options.
On-Premises — Full deployment on municipal infrastructure.
Canadian Cloud — Managed deployment on Canadian IaaS.
Hybrid — Core services on-prem with cloud analytics.