The American Museum of Natural History's scientific computing system now carries roughly 3PB of research data, with 95% of traffic belonging to read-intensive workloads, and it has run for four years without any data integrity issues detected. We don't read this as a story about "storage costs being eliminated outright." Rather, it's research infrastructure starting to adopt a more flexible combination: the institution retains ownership of its data while handing off hardware operations to an open storage network provider.

What this is

AMNH works with an Open Storage Network (OSN — a partner that manages local hardware collaboratively and provides remote operations), connecting standard servers and disk arrays to S3-compatible storage, then mounting the object storage as a file system through JuiceFS Community Edition, so compute clusters can access remote data the same way they access ordinary disks.

This architecture serves large-volume reference data such as genome sequences and astronomical survey data: data is written once and then read repeatedly, with little modification. AMNH places data consistency ahead of performance, repeatedly tests during the proof-of-concept phase, and continuously monitors logs and metrics.

Worth noting: write operations against object storage did produce timeout warnings, but no data corruption resulted. JuiceFS handles exceptions through a unified retry mechanism, avoiding part of the risk. As for write-back (writing first to a local cache, then syncing asynchronously), it improves write throughput but raises the requirements placed on local disks and backups.

Industry view

We believe the most valuable part of this case isn't a single piece of software, but its replicability: object storage carries capacity and hardware management, the file system layer provides compatible access, and the research institution still controls the data and the underlying devices. This model is attractive to universities, museums, and labs with limited budgets that still need PB-scale storage.

But the risks are equally clear. S3-compatible does not mean every storage backend behaves identically on timeouts, retries, and consistency; write-back can also widen the window for data loss. AMNH's current workload is predominantly read-only, so this combination cannot be taken as direct proof that it suits write-heavy operations, real-time collaboration, or workloads with strict job scheduling. Remote operations by an OSN provider also mean the institution must define fault response, data migration, and takeover responsibilities if the vendor exits.

Impact on regular people

For enterprise IT: Companies can reassess the cost boundary between self-built storage and cloud object storage, using the file system as a transitional layer — but they must load-test against real read/write ratios and define data consistency SLAs (specific commitments on service availability and data reliability).

For individual careers: Data platform, infrastructure, and research support roles will keep accumulating the combined skill of "storage architecture + reliability validation"; knowing how to configure object storage alone may not be enough to stay competitive.

For the consumer market: There won't be direct product changes for ordinary consumers in the short term, but lower-cost data preservation and compute may progressively underpin larger-scale online model training, scientific retrieval, and generative AI services.