Technology

Google Cloud Storage

Google Cloud Storage (GCS) is Google's fully-managed object storage service — buckets with per-object storage classes (Standard, Nearline, Coldline, Archive), strong global consistency, and automatic tiering via Autoclass. Alongside its native JSON/gRPC API it exposes an **S3-interoperable XML API with HMAC keys**, so S3 SDKs and tooling can target GCS with minimal change. It is one of the big-three hyperscaler object stores alongside [AWS S3](/node/aws-s3) and Azure Blob Storage.

5 connections 1 post

Definition

What it is

Google Cloud Storage (GCS) is Google's fully-managed object storage service — buckets with per-object storage classes (Standard, Nearline, Coldline, Archive), strong global consistency, and automatic tiering via Autoclass. Alongside its native JSON/gRPC API it exposes an **S3-interoperable XML API with HMAC keys**, so S3 SDKs and tooling can target GCS with minimal change. It is one of the big-three hyperscaler object stores alongside [AWS S3](/node/aws-s3) and Azure Blob Storage.

Why it exists

GCS matters to this index on two counts. It is a peer object store and a common S3 migration source/target — its S3-interop XML API makes it directly addressable by the S3 ecosystem this index maps. And in 2026 its center of gravity shifted toward being an **AI-training storage substrate**: Google's "Cloud Storage Rapid" family re-architects object storage specifically to keep GPUs and TPUs fed, the same object-storage-as-active-memory-tier thesis this index tracks across AWS, MinIO, VAST, and WEKA.

Primary use cases

general-purpose object storage; multi-cloud / S3-interoperable workloads; AI/ML training data and checkpoint I/O; analytics data lakes (BigQuery/Dataproc-adjacent); backup and archive tiers.

Recent developments

Latest signals
  • Cloud Storage Rapid launched at Google Cloud Next '26 — object storage rebuilt for AI. Two components: Rapid Bucket (a high-performance zonal object store delivering >15 TB/s aggregate read throughput, up to 20M QPS, and sub-millisecond latency) and Rapid Cache (formerly Anywhere Cache — accelerates reads on existing buckets with no code changes, up to 2.5 TB/s). Rapid Bucket reported 50% less blocked GPU time, up to 2.5× faster data loading for multi-modal training, 5× faster checkpoint restores, and 3.2× faster writes vs traditional object storage. Per Cloud Storage Rapid turbocharges object storage for AI, analytics (Google Cloud) and Rapid high-performance storage docs.
  • Rapid Cache "ingest on write" kills the cold-cache penalty — and Anthropic is a named user. The new ingest-on-write feature writes to cache simultaneously with the bucket write, eliminating the initial cache-miss and giving up to 2.2× faster checkpoint restores. Anthropic uses Rapid Cache to co-locate data with TPUs in a single zone with dynamically scalable read throughput up to 2.5 TB/s. Per Next '26 storage announcements (Google Cloud) and Rapid Cache docs.

Connections 5

Outbound 5
scoped_to2
Object StorageS3
alternative_to1
AWS S3
solves1
Data Loading Bottleneck
enables1
Training Data Streaming from Object Storage

Featured in

2026-07-05 The Frontier Moved Again — and the Floor Compounded In June we argued the AI stack had split into a closed, expensive frontier and an open, cheap floor. Six weeks later the frontier proved the point the hard way: Claude Fable 5 was pulled offline for 19 days by an export-control order, then restored with a retention mandate that quietly bars the most sensitive data from ever touching it. Meanwhile the floor didn't just hold — it compounded. Object storage got RDMA-fast, the query engines converged on one substrate, and the data plane grew a control plane built for agents instead of humans. This is the field report.