Object storage
Storing files and media outside the database: buckets, objects, pre-signed links, storage classes, lifecycle, versioning, and the mistakes that expose data or cost a lot.
- 32 cards
- 3 topics
- Free
The outline, topic by topic
Each topic is weighted the way the exam weighs it.
- Concepts
- Scenarios
- Trade-offs and failures
A few cards from the deck
Object storage: what is it?
Show the answer
Storage of files (objects) addressed by a key in buckets, reached through an HTTP API.
It absorbs almost unlimited volumes at low cost.
Profile photos are stored in the database and bloat it. What do you do?
- Put them in object storage; the database keeps only their key
- Enlarge the database disk
- Compress them in the database
- Cache them
Show the answer
Put them in object storage; the database keeps only their key
The database stays light and fast, and files are served separately.
Bucket: what is it?
Show the answer
A named container of objects, with its own access rules.
Permissions are set at bucket and object level.
A bucket is made public by mistake. What risk?
- A leak: its files are readable by anyone
- Storage slows down
- Files are deleted
- None
Show the answer
A leak: its files are readable by anyone
It is one of the most frequent causes of data leaks.