File Systems and Databases as Complements
They work best as layers, not rivals.
Senior Editor
Owen Marroquin covers Object Storage for Storage Letter, turning dense material into guidance readers can act on.
16 stories
They work best as layers, not rivals.
Breaking cold-start delays into three distinct infrastructure bottlenecks reveals practical fixes.
Multiple hidden charges stack on every gigabyte of S3 data you move.
Four tools mount S3 as a filesystem, each with different tradeoffs on speed and POSIX compatibility.
Design S3 data lake zones and partitions around query patterns, not data arrival.
Assess which workloads truly need block storage before redesigning applications for object storage.
Egress fees make switching cloud vendors prohibitively expensive for most organizations.
Gateway endpoints eliminate NAT routing costs and latency ceilings for same-region S3 access.
Object storage scales across regions where SAN and NAS hit hard limits.
Four self-hosted alternatives and two managed options fill the gap MinIO's archival left behind.
Agents overwhelm storage billing because their unpredictable loops break provisioned pricing.
LLMs already fluently speak bash, making it the universal agent interface.
How parallel agents can safely share files without losing data to race conditions.
Storage layers must bridge the gap between ephemeral sandboxes and stateful agent workflows.
Agents that remember across sessions outperform those reset every time you open them.
How GPU-native processing and open table formats are reshaping S3 data lake design.