Design Considerations of a Blob Store
In this lesson2 sections
Design Considerations of a Blob Store
Chunking makes large objects manageable, but it creates metadata and recovery work. This lesson follows those costs through partitioning, listing, replica placement, and garbage collection.
Introduction
The previous lesson outlined the major components of the blob store. This lesson examines implementation challenges, including storing large blobs, managing replicas, and optimizing retrieval latency. The following table summarizes the lesson objectives.
Design questions
| Section | Purpose |
|---|---|
| Blob metadata | This is the metadata that’s maintained to ensure efficient storage and retrieval of blobs. |
| Partitioning | This determines how blobs are partitioned among different data nodes. |
| Blob indexing | This shows us how to efficiently search for blobs. |
| Pagination | This teaches us how to conceive a method for the retrieval of a limited number of blobs to ensure improved readability and loading time. |
| Replication | This teaches us how to replicate blobs and tells us how many copies we should maintain to improve availability. |
| Garbage collection | This teaches us how to delete blobs without sacrificing performance. |
| Streaming | This teaches us how to stream large files chunk-by-chunk to facilitate interactivity for users. |
The rest of this lesson is for Premium members
Premium opens every lesson in this course, along with all questions and solutions on PracHub.