The roadside platform is the low-latency edge and ingestion layer for the Beaus tolling ecosystem. It is intentionally separated from the back-office repository so device operations, image evidence capture, and lane event throughput can evolve on an independent release cadence while still sharing contract and governance standards with the back-office platform.
- ingest lane passage, gantry, and reader events at high volume
- track roadside device state and operational health
- normalize and publish evidence-ready Kafka events for downstream tolling workflows
- preserve strict separation from operator-facing back-office domains and release cycles
.
├── docs
├── infra
│ └── k8s
├── platform
│ ├── bom
│ └── contracts
├── services
│ ├── device-management-service
│ ├── image-evidence-service
│ └── lane-event-ingest-service
└── tools
- Back-office platform: phamhungptithcm/beaus-tolling
- Shared event and naming discipline: platform/contracts/README.md
- Technical direction and governance: docs/README.md
- Roadside services own raw capture, device telemetry, and evidence pipelines.
- Back-office services own customer, case, payment, and operator workflows.
- Integration happens through Kafka events and signed APIs rather than shared databases or tightly coupled schemas.
- Reliability, observability, and safe releases matter more than packing multiple responsibilities into a single service boundary.