Technical Specifications
Technical Architecture
Civic Transit is built on a modern, event-driven microservices architecture designed for transit-grade reliability — 99.9% uptime SLA with real-time vehicle tracking at 15-second intervals, GTFS-RT feed generation, and graceful degradation during connectivity events.
99.9%
Uptime SLA
5,000+
Concurrent Users
<200ms
API Response
11
Platform Modules
Architecture Overview
Each transit domain is an independently deployable service with its own data store, API, and scaling characteristics. Services communicate via Kafka events for real-time data flow and REST APIs for synchronous queries.
Platform Modules
Core Services
Independently deployable microservices with dedicated data stores and APIs.
Total Modules
11
Protocol
REST / gRPC
Bus
Async Events
Container
Kubernetes
Database
PostgreSQL 16
Specifications
Technical Details
Browse specifications by category. All values reflect current production configuration.
AVL Processing
15-second GPS position updates from 500+ vehicles with < 2s processing latency
Prediction Accuracy
Arrival predictions within ±60 seconds for 90%+ of stops
API Response
< 150ms P95 for GTFS-RT feed requests; < 200ms for trip planning queries
GTFS-RT Feed
TripUpdates and VehiclePositions refreshed every 15 seconds for all active trips
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.