Object Storage Under the Hood: PUT, GET, and Erasure Coding
Under the API, an object store is a distributed log of immutable objects plus a metadata service. We trace the full path of a PUT — checksums, multipart upload, erasure coding across servers — and the GET path through metadata lookup and data node selection. Then we look at why listing and consistency behave the way they do: metadata partitions, global index buckets, and the trade-offs behind read-after-write consistency in modern stores. We also cover versioning as an append log, lifecycle rules, and how storage classes trade durability for cost.
Topics covered:
- PUT/GET paths: metadata first, then data
- Erasure coding and durability math
- Metadata partitioning and hot shards
- Versioning, lifecycle, and storage classes
Related articles
Object Storage vs. Block Storage
S3 versus EBS: key-value HTTP APIs versus raw device semantics, strong read-after-write consistency, and the real math behind 99.999999999% durability.
Containers Aren't Lightweight VMs
Namespaces, cgroups, seccomp, and the real isolation boundaries — what containers actually isolate and what they don't.
Vendor Lock-In Is a Cost Model
Egress fees, control-plane APIs, and data gravity — how cloud providers price switching costs, and how to compute the real cost of a migration.
More in Cloud & Infrastructure
Edge Computing Explained: Where Compute Actually Sits
What edge computing actually is — the compute tiers from device to far edge to cloud, latency and bandwidth budgets, and which workloads genuinely benefit.
DetailsContainer Orchestration Basics: API Server, Controllers, and Scheduler
Container orchestration from first principles — what the API server, controller manager, and scheduler actually do, with Kubernetes as the working example.
DetailsThe Cost of Distributed Systems: Coordination, Consistency, and Failure
What distributed systems actually cost — coordination, consistency, and failure taxes — quantified with quorum math, tail latency, and retry-storm dynamics.
DetailsDNS and Traffic Routing in the Cloud: From Resolver to Anycast
How DNS actually routes traffic in the cloud — record resolution, CDN anycast, geo routing, load balancer handoffs, and how TTLs shape your failover story.
DetailsMulti-Region Architecture: Active-Active, Failover, and Replication
The real mechanics of multi-region deployments — where writes land, how replication propagates, what failover flips, and the latency math that constrains every design.
DetailsAutoscaling Explained: The Controller Loop Behind Horizontal Scaling
How autoscaling actually works — the metrics window, desired-replica calculation, stabilization, and why naive CPU-based scaling oscillates under real load.
DetailsServerless Cold Starts, Measured: Where the Latency Actually Goes
Measured cold-start latency across Lambda, Cloud Functions, and container runtimes — what actually takes time and which optimizations genuinely reduce it.
DetailsKubernetes Scheduling Visualized: The Filter-Score Pipeline
What the Kubernetes scheduler actually does — how pending Pods become assigned to Nodes, the filter-then-score pipeline, and how taints and affinity shape placement.
DetailsContainer Images Explained: Layers, Manifests, and Digests
How container images are actually built and run — layers, manifests, content digests, and what the runtime does at pull and run time.
DetailsDepth, delivered weekly
One technical dispatch a week — articles and episode notes before they go public.
One technical dispatch per week. No noise.