Block storage begins as a disk
An operating system can place a filesystem on a block device and use it for software or application data. I want you to distinguish the volume from the files inside it. Disk access and shared-folder access are different requirements.
File storage supports filesystem behaviour
Applications expecting shared folders need a suitable protocol, permissions and concurrency behaviour. Decide how many clients access the data and how writes are coordinated. Sharing a filesystem does not automatically make every application safe for multiple writers.
Objects use service operations
Object storage works through object operations rather than behaving as a normal attached disk. It can fit media and many application datasets. Check the software interface before replacing existing storage; a different interface may require an application change.
Try it yourself
Classify an OS disk, departmental share and uploaded website images. Explain the access pattern behind each choice.
A common question
Can object storage replace every filesystem?
No. Applications depend on particular interfaces and semantics. Confirm compatibility before changing the storage model.
References & video notes
Use the video to follow the topic with me. Console screens and older offers can change, so check the current AWS documentation before performing a lab.
Keep learning
- Instance store vs EBS: where should your data live?
- EBS volume types: understand IOPS and throughput
- EBS snapshots: include a restore in your backup lab