Object, block, and file storage
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
pick the right storage type per use case.
Planned topics
- Object storage: files addressed by key over an HTTP API; huge scale, cheap, ideal for media, documents, logs, backups; not a disk.
- Block storage: raw disks attached to one VM or container; fast, for databases and boot volumes.
- File storage: shared network file systems with folders and permissions; for lift-and-shift apps needing shared files.
- Default to object storage; use block or file only when the workload demands them.
- Durability (not losing data) and availability (reaching data) are different promises.
Draft outline details
Demonstration
a three-row table: storage type, access method, typical Larkspur use (product images: object; database volume: block; legacy label tool shared folder: file).
Check your understanding
Which storage type suits millions of product images served via CDN?
Show answer
Object storage.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.