AWS S3
-
An intro to DeepSeek’s distributed file system (3FS) - Architecturally, it is a scale-out metadata filesystem1. Other related distributed file systems are Collosus, Tectonic (Meta), ADLSv2 (Microsoft), HopsFS (Hopsworks), and I think PolarFS (Alibaba). They all use different distributed row-oriented DBs for storing metadata. S3FS uses FoundationDB, Collosus uses BigTable, Tectonic some KV store, ADLSv2 (not sure), HopsFS uses RonDB.
- MinIO - a high-performance, S3-compatible object storage solution released under the GNU AGPL v3.0 license.
see also
- Migrating from AWS to Hetzner
- Replacing EBS and Rethinking Postgres Storage from First Principles
- EBS costs for allocation
- EBS is slow at restores from snapshot (faster to spin up a database from a Postgres backup stored in S3 than from an EBS snapshot in S3)
- EBS only lets you attach 24 volumes per instance
- EBS only lets you resize once every 6–24 hours, you can’t shrink or adjust continuously
- Detaching and reattaching EBS volumes can take 10s for healthy volumes to 20m for failed ones, so failover takes longer
Written on September 12, 2025, Last update on October 18, 2025
aws
S3