Main content
Routes · Through a pipeline
Storage
What happens to bytes once they land, and what that decides for every read after.
- 1Storage: Physical OrganizationWhat should sit next to what, given that I must decide at write time and find out at read time?
- 2Persistence & DurabilityWhen a system says "yes, your data is safe", what exactly has it promised, and what did it have to do to keep that promise?
- 3Encoding, Serialization & CompressionWhat do we turn our values into when we turn them into bytes, and what does that choice cost?
- 4IndexingWhen does a separate "where is it?" structure pay for itself, and what does it cost to keep it true?
- 5Table & Storage MaintenanceWho pays for the gap between the order data arrives in and the order it is read in: the writer, every reader, or a background job, and what is the break-even?