Your company wants to track whether someone is present in a meeting room reserved for a scheduled meeting. There are 1000 meeting rooms across 5 offices on 3 continents. Each room is equipped with a motion sensor that reports its status every second. The data from the motion detector includes only a sensor ID and several different discrete items of information. Analysts will use this data, together with information about account owners and office locations. Which database type should you use?

NoSQL is the best choice due to the high volume and velocity of data (1000 sensors reporting every second). NoSQL databases, particularly wide-column or document stores, handle large-scale, high-throughput data ingestion efficiently and scale horizontally to accommodate growth. The data's discrete nature and the need to combine it with other information (account owners, office locations) suggest a flexible schema, which NoSQL databases excel at. Relational databases would struggle with the write-heavy, high-volume nature of the sensor data, potentially leading to performance bottlenecks and complex scaling challenges. Flat files lack the indexing and querying capabilities needed for analysis. Blobstore is for unstructured binary objects, not structured sensor data.