Learning series · 5 episodes · Senior / Staff / Principal
The Object Exists. Is It Safe?
Six investigations into storage interfaces, multipart publication, object consistency, erasure coding, silent corruption and safe reclamation.
Start series →Follow the decisions in order
- Part 1 of 6
Senior
The bytes are durable. Why can't the database use this object bucket as its disk?Classify storage by operations, mutation granularity, namespaces and durability contracts.
- Part 2 of 6
Staff
The 200 GB upload finished. Why shouldn't we show the file yet?Separate part acceptance, checksums, completion, conditional catalog publication and cleanup.
- Part 3 of 6
Principal · AI Engineering reading
How do you stop an answer from mixing two document versions?Distinguish strongly consistent PUT, GET and LIST from a transactional dataset release.
- Part 4 of 6
Staff
Three copies cost too much. Will six data shards and three parity shards be safer?Derive redundancy overhead, recovery thresholds, placement risks and repair IO.
- Part 5 of 6
Staff
The backup was written five years ago. How do we know its bytes are still correct?Detect latent corruption using expected checksums, scheduled scrub work and verified reconstruction.
- Part 6 of 6
Principal
The cleanup job deleted the chunks. Why were active files still using them?Protect committed manifests from stale mark-and-sweep decisions, delayed DELETE and ABA.