Millions of parking-meter heartbeats arrive each hour and overwhelm a single primary database writer. Which NoSQL-oriented strategy best addresses this write pressure?
Select an answer to reveal the explanation.
Short Explanation
When meters scream all at once, one lonely writer melts. Horizontal NoSQL scale spreads those writes across many nodes. More lanes for the traffic, not a taller single toll booth.
Full Explanation
High-ingest civic telemetry such as parking-meter heartbeats requires write paths that scale out across nodes. Distributed NoSQL systems commonly partition writes so no single primary absorbs the entire ingest load. Vertical scale alone eventually hits hardware and operational limits for this volume. Horizontal write scalability is a core reason municipalities adopt NoSQL for telemetry-heavy workloads.