Dispatchers need second-level visibility into ambulance-bay status, but the current feed is a nightly FTP of CSV dumps. Why is that pattern a poor fit?
Select an answer to reveal the explanation.
Short Explanation
A once-a-night USB drop cannot steer a live bay board. Messaging gives velocity; nightly FTP is batch luggage. For second-level ops, the bus beats the overnight folder.
Full Explanation
Batch file transfers such as nightly FTP of CSVs serve archival or daily reporting well but cannot sustain second-level operational dashboards. Messaging systems supply continuous velocity so consumers update as events arrive. Claiming FTP is inherently more accurate, that Kafka cannot carry facility status, or that annual extracts suffice for live ops confuses batch analytics with real-time ingestion needs. Choosing the right ingest tempo is a Chapter 8 judgment call.