Utility telemetry arrives as a write-heavy stream (Amazon Kinesis into Amazon DynamoDB), while an open-data catalog is read-heavy with relatively few writes. What capacity and key-design mindset should the architect apply?
Select an answer to reveal the explanation.
Short Explanation
A firehose of meter ticks is a write problem; a popular catalog is a read problem. Do not dress them in the same capacity suit—shape keys, buffering, and reads around how the traffic actually flows.
Full Explanation
Write-intensive telemetry paths need partition keys and write capacity (and often streaming buffers such as Kinesis) that avoid hot partitions under sustained ingest. Read-intensive catalogs benefit from read capacity planning, caching, or read replicas depending on the engine. Treating both as identical, or collapsing them onto one underspecified relational host without regard to access mix, risks throttling and poor performance.