schema_version: 1 decision: id: broker-for-tracking-events title: A message broker for tracking events status: accepted date: 2026-09-08 elements: [message-broker, telematics, driver-app, tms, tracking-event] diagrams: [0300-technology/infrastructure.archify, 0200-application/application-cooperation.archify] context: > Handhelds and telematics units posted every scan and position straight to the TMS. At evening peaks the TMS fell behind and dropped events when a device retried over a weak signal. decision: > Devices publish tracking events to a Kafka message broker on the cloud cluster. The TMS and telematics read the topics at their own pace; events are kept for seven days for replay. consequences: > Spikes no longer reach the TMS. Status on the tracking portal can lag by seconds. Consumers must handle duplicate events, and the broker is one more platform service to run.