Topic
S3-style flat-namespace storage accessed over HTTP with per-object metadata, versioning, lifecycle tiering and replication.
Cloudflare opened K2, a serverless event log built on R2 object storage, to public beta at about one second of p99 produce latency. For that wait, teams get producers decoupled from consumers and no Kafka cluster of their own to run.
Reality
Operators running Stalwart for a 10,000-mailbox university keep settings in PostgreSQL and messages in S3 storage, so no mailbox sits on one machine's disk. Their mailcow and Mailu verdicts come from documentation, where failover means a cold standby or a shared ReadWriteMany volume.
Reality
ClickHouse records a disk for every part, so a TTL rule can age old months onto S3 with the queries untouched. The lab behind the write-up substitutes MinIO for S3, so the latency half of the trade is still unmeasured.
Reality
Munchable's nightly GitHub Actions job writes a full dump kept about 30 days plus a catalogue-free core dump kept a year. The preflight that fixed its first failure reads only the host and port out of the connection secret.
Reality
A dev.to walkthrough CNAMEs a customer subdomain to platform storage and keeps every permission in the signature. Its sample onboarding code puts the tenant check before the presign call, where it belongs.
Reality
Strong read-after-write consistency and conditional writes are real guarantees, but only two of the four database behaviours they stand in for have an enforcement point in the service, and the other two are convention.
Reality
Archiving a project with a billion Docker pulls turned an object store into an audit finding. Docker's extended support does not remove the migration, it moves the deadline out to 2031.
Reality
A dev.to writeup reduces the storage choice to a property test on the calling code. The part worth arguing about is when each wrong answer shows up: on the first query, or at 10 million files.
Reality