Skip to content
academia.sh

Course Intermediate

Storage and Data in the Cloud

Published Updated

By the end of this course

Start course

01

Storage Types

Where data lands: how the bucket, object, and key model differs from a file system, the price and retrieval trade-off of storage classes by access frequency, the automatic transitions and deletions of versioning and lifecycle rules, block storage's volume types and IOPS budget, the multi-writer use of a shared file system, the archive tier's retrieval time, and presigned URLs that grant time-limited access.

  1. 01 Object Storage Separating the bucket, object, and key model from a file system item by item: prefix instead of directory, copy instead of rename, no partial update, and listing as a billed operation; translating every difference into request counts and bytes, and counting the key layout as an unrecoverable item.
  2. 02 Storage Classes Measuring tiers by access frequency: how the storage fee and the access fee run in opposite directions, scanning the break-even access frequency by object size, distributing objects into classes over access history, and counting the wrong class both ways — the annual cost of keeping infrequent data in the frequent class, and frequent data in archive.
  3. 03 Versioning and Lifecycle Rules Running automatic transitions and deletion over a 36-month object lifetime: the bytes that accumulate without a rule, the number of objects transitioned and deleted by the rule, the transition fee swallowing the gain on small objects, an early transition's retrieval cost, and the deleted object not actually being deleted once versioning is turned on.
  4. 04 Block Storage How a volume's type and size give an input/output budget: applying workload profiles to that budget, counting the saturation point and the idle budget, the design trap opened by size and performance being tied together, and the volume's inability to shrink and its binding to a single instance.
  5. 05 File Storage Measuring the shared file system under multi-writer access: keeping the same data as object, block, and shared file and counting how many instances can write at once, how the lock works, latency, and monthly fee; naming the case where the shared file system gains nothing, and working out the access protocol as an unrecoverable item.
  6. 06 Archive Storage How the archive tier's storage fee drops while retrieval is both billed and delayed: scanning three retrieval speeds along with their time and fee, working out how many hours an audit request waits, the egress fee stacking on top of retrieval, and the minimum retention period making an early-deleted object pay the full period.
  7. 07 Access Control and Signed URLs Measuring time-limited, narrow access: generating a presigned URL with a fictional key and actually verifying its lifetime, method, and scope checks; scanning link lifetime to compare regeneration load against the leak window, counting the surface scope width opens, and showing a presigned URL's unrecoverability through its cancellation blast radius.

02

Managed Data Services

Handing off database operation: the decisions a managed relational database's backup, patching, and failover automation take over, spreading read load across read replicas and the cost of lag, how the partition key and capacity model fix the access pattern in a managed key-value service, secondary indexes and change streams, the managed cache service, zonal and internet egress pricing, and snapshots with point-in-time restore.

  1. 01 Managed Relational Database An item-by-item comparison of a self-run relational database against the managed service: how many of 28 decisions go to the provider, how many stay with you, and how many become inaccessible altogether; how many of the kept items turn out to be one-way; the failover window split into the provider's fixed share and the application's share, with dropped requests measured across five cache lifetimes; and the data's exit costed as logical export time plus egress fee.
  2. 02 Read Replicas Measuring how replica lag reflects onto the application: in a stream of 420,000 requests, lag is scanned from 0.1 to 5 seconds and, at each value, the count of stale reads and of requests unable to see their own write is derived; a session-based sticky window's saved requests are compared against the read share it shifts to the primary; how both the per-replica gain and the lag change as replica count rises is counted; and the monthly transfer cost of an out-of-region replica is computed.
  3. 03 Managed Key-Value Service Measuring the choice of partition key across three candidates against a real key distribution: requests per partition and the busiest partition's share for each candidate, and access patterns the key does not support counted as unserved queries; provisioned capacity compared against the per-request model on the same load profile, with the over-provisioning the hot partition forces computed; and the cost of changing the partition key worked out in duration and fictional units.
  4. 04 Secondary Indexes and Streams Recovering the previous lesson's three unserved access patterns with a secondary index, and counting what that costs in return: each index's recovered requests, the extra write cost it adds, the stale-result share caused by storage and index lag, the trade-off between projection choice and round trips to the base table, and a change stream modeled with a consumer — measuring event order, reprocessed events, and the missed window once the stream's retention runs out.
  5. 05 Managed Cache Service Measuring the renting of the in-memory layer as a service: two scaling axes giving the same hit rate and the same bill, the 100% hit-rate row turning out the most expensive, the 3,370,000 keys lost when a node changes putting the purchased capacity 325% over, warm-up not shortening with shard count, and a cache in another zone writing a 722-unit transfer item and coming out pricier than no cache at all.
  6. 06 Data Transfer and Egress Cost Measuring zonal and internet egress: the same 6,180 GB running 1,440 units in a single zone, 4,380 in two zones, 7,320 across two regions; compression cutting 1,463 units while a second read replica adds 1,400; the same 1,000 GB costing zero coming in and 9,000 units going out; and the 33,600 GB accumulated over 24 months costing the same as 69 months of billing to export.
  7. 07 Backup and Restore Comparing the snapshot against the continuous log: scanning frequency and counting the lost window together with the storage fee, a 24-hour snapshot plus a 7-day log coming out both cheaper and sixty times narrower than an hourly snapshot, restore time splitting into four components with a 58-minute baseline, and the portable copy's extra cost — starting at 301 units a month — because backups sit in the service's own format.

Final exam

Storage and Data in the Cloud — Final Exam

In preparation

This course's question bank is not complete yet. The exam opens here automatically once enough questions are added.

Start typing to search.

↑↓ ↵ Esc navigate · open · close