A smart-city architecture office must choose ingest patterns: streetlight controllers emit sub-second voltage samples, while the finance system exports ledger files once each night. How should the team match ingest frequency to those needs?

High-performing data architectures match ingest style to latency and volume characteristics: continuous streaming services for sub-second telemetry, and scheduled or batch transfer for nightly finance extracts. Homogenizing both into infrequent physical transfers or extreme device-side buffering adds latency where freshness matters. Compelling stable nightly exports onto streaming infrastructure adds cost and complexity without business need. Select streaming versus batch based on required freshness.