Volume choice is IO-shape matching: burst buckets, provisioned IOPS and throughput designs behave very differently under mixed OLTP-plus-batch load. Average latency graphs hide the failure entirely.
an account raises the per-topic limit · no card
← Cloud Platforms & Architecture / 15
mediumNewAmazon & AWSPhonePeGoldman Sachs
Pick an EBS volume type for a Postgres primary with a nightly analytics batch. What decides it?
Volume choice is IO-shape matching: burst buckets, provisioned IOPS and throughput designs behave very differently under mixed OLTP-plus-batch load. Average latency graphs hide the failure entirely.
Updated Sep 2026 · Grounded in researched DevOps, SRE and platform engineering interview loops, written to a senior-engineer editorial bar, and never padded to hit a word count.
UP NEXT ON YOUR JOURNEY
Next in this trackReads are drowning our database primary. Someone suggested Multi-AZ. Does that help, and if not, what does?Next in this trackA DynamoDB table provisioned at 6,000 writes per second throttles at 2,000. The partition key is a date shared by many items. Fix it.Next in this trackWhere does Redis actually earn its keep in production, and which of its features disappoint teams?
DISCUSSION · 0
Nothing here yet. Say how you would answer it.