Do you happen to be the writer of this technical article on AWS? [1] If not, someone on Seth Markle's team over at Amazon wrote a pretty fascinating article on

Do you happen to be the writer of this technical article on AWS? [1] If not, someone on Seth Markle's team over at Amazon wrote a pretty fascinating article on the S3 architecture. Never actually heard the "airplane at 75 MPH over a grass lawn comparison" before. This [2] aggregate workload graph/video is pretty sweet too. Very matrixy while still actually being fairly clear about what's going on. Imagery implies S3 (at writing) had a 3.7 PB bucket size with 2.3M req/sec. Worked out to 143 hard drives (storage constrained result) and 19,000 hard drives for the I/O constrained result. Kind of an interesting counterpoint to the article. Here's what really large workload / access rate systems with spikey, intermittent workloads are structured like. [1] https://www.allthingsdistributed.com/2023/07/building-and-operating-a-pretty-big-storage-system.html https://www.allthingsdistributed.com/2023/07/building-and-op... [2] https://www.allthingsdistributed.com/videos/fast-agg-graph-compressed-small.mp4 https://www.allthingsdistributed.com/videos/fast-agg-graph-c...