Roadside Architecture
Purpose
The roadside platform is responsible for:
- lane pass-through capture and event normalization
- transponder, controller, and field-device heartbeat processing
- image and evidence ingestion workflows
- publication of roadside domain events for downstream tolling operations
Architectural Intent
Roadside is optimized for sustained ingest throughput, low-latency device interactions, and resilient event delivery. It should remain operationally independent from the back-office platform so operator features, case workflows, and payment changes do not slow down roadside releases.
Boundary Model
- Roadside owns raw event capture, evidence lifecycle, and field-device operational state.
- Back-office owns customer, trip resolution, case management, fulfillment, reporting, and payment orchestration.
- The repos are connected through Kafka contracts and signed APIs, not shared schemas or direct database writes.
Core Services
lane-event-ingest-service: normalizes lane, gantry, and reader events into canonical trip-capture payloadsdevice-management-service: tracks device status, heartbeat freshness, alarms, and maintenance stateimage-evidence-service: manages image evidence ingestion, storage references, and downstream matching metadata
Scale Posture
- tolerate burst-heavy roadside traffic without coupling ingest latency to operator workflows
- prefer asynchronous event handoff over synchronous cross-domain dependencies
- isolate failure domains so a back-office incident does not interrupt roadway capture