I’ll also add that DDB would be unfathomably expensive for that type of workload. With 1,000,000 writes per second it would cost $3.25M /month with on demand pricing, or $93K/month with provisioned capacity and an annual agreement. That doesn’t include storage or reads. They were running on a 4 thread EC2 VM, so like $60/mo with a nice NIC. TSDBs are really good at logging, storing, and aggregating lots of floats efficiently. DDB shines for storing documents like product pages and returning them in ms or microseconds with a DAX cache, even with thousands of requests per second.
I believe it's a use case for RedShift if anything, not DynamoDB.
RedShift is column oriented, if there is some types for numbers/timeseries, that should be able to do the job. It might still be cost prohibitive though.
I personally find the 1M writes to be misleading. It's typically 1000 sensors generating 1000 metrics (a large key=value file). It should be ingested in batch. I guess it's not impressive enough if you call it 1000 requests per second.
