Published lesson · 35 minutes

Choose cloud storage and protect data

Objective: Match object, file and block storage to a basic use case, distinguish a managed database from a file store, and plan access, backup and deletion.

Start with the user need

Storage is chosen by how an application uses information. Object storage is well suited to separate files such as images; file storage exposes shared folders; block storage provides disk-like volumes. Managed databases organize structured records and support queries. Separate public assets from private records. Define what data is collected, who can read or change it, how long it is kept, and how it is backed up and removed. Use synthetic data in all course exercises. The fictional website stores public event images and registration records that must not be exposed to everyone.

Make the trade-offs clear

For a small learning exercise, keep names and records fictional. First state the user need, then select the simplest design that meets it. Compare the benefit with a limitation such as connectivity, service dependency, configuration effort or recurring cost.

Use object storage for individually addressed files such as approved public images.
Use a database for structured records that need validation and queries; choose access controls deliberately.
Encrypt data in transit and at rest where supported, and restrict public access to only the assets intended to be public.

A cloud design is a set of trade-offs rather than a promise. Record assumptions about expected users, sensitive information, connectivity and the people who will operate the service. Revisit those assumptions when the audience or risk changes.

Practice scenario: The fictional website stores public event images and registration records that must not be exposed to everyone. Map three fictional data items—public event image, registration record and daily export—to suitable storage. Specify who may access each, a retention rule and one recovery check.

Worked examples