A smart-city IoT desk lands varied sensor payloads whose shapes keep changing and cannot wait for one universal upfront schema. Which approach aligns best?
Select an answer to reveal the explanation.
Short Explanation
Sensors are messy and change their outfits often. Schema-on-read means land the data first and figure out the shape when you query. Waiting for a perfect universal schema just piles unread packets at the door.
Full Explanation
Schema-on-read approaches store diverse payloads without requiring a complete shared write-time schema, interpreting structure during analysis. Varied municipal IoT feeds evolve faster than rigid schema-on-write gates allow. Forcing universal upfront columns delays ingestion and drops useful telemetry. Flexible NoSQL and Big Data landing patterns embrace schema-on-read for this class of civic sensor data.