root-at-skic
0745de822a
Six example models next to the three C4 ones: arc42 (Cinema Tickets, IoT Telemetry, Team Wiki) by section, ArchiMate (Insurance Claims, HR Onboarding, Logistics Tracking) by layer, each validated with 0 errors and 0 warnings. resolveRefs and the editor schemas now take ref: in workflow and dataflow nodes, sequence participants and lifecycle states, as the skill already did. Example tests check each framework's folders.
21 lines
915 B
Plaintext
21 lines
915 B
Plaintext
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.
|