Intermediate everything in Cloud Platforms, page 7
Cross-Region Replication (CRR): Geographic Data Copying
Cross-Region Replication automatically copies data to another geographic region, like a live backup. Use it for disaster recovery, lower latency for global users, or compliance. The footgun: it only copies *new* objects, not what's already in the bucket.
Block Storage Snapshots Are Incremental Backups
A snapshot is an incremental, point-in-time backup of a disk volume, saving only changed data blocks. Use it for disaster recovery to restore a volume's exact state. The footgun: deleting an older snapshot may not save money if a newer one needs its data.
Cloud Storage Tiers: Match Cost to Access Frequency
Storage tiers match data cost to access frequency. 'Hot' tiers are fast and expensive for active files; 'cold' tiers are cheap for archives. Use for data that cools over time, like logs. The footgun: retrieving cold data unexpectedly is slow and costly.
Data Durability vs. Availability: Lost vs. Unreachable
Availability is "can I reach my data right now?" while durability is "will my data still exist tomorrow?". Cloud storage systems are designed for both, but they solve different problems: network outages vs. data corruption.
User Data Scripts: Day-One Instance Configuration
User data scripts are your instance's "Day One" instructions, automatically running commands like package installs on first boot. Use it to set up a web server or install agents without manual SSH.
AWS Reserved Instances: Commit to Compute, Save Big
Reserved Instances are like leasing a car instead of renting daily: commit to 1-3 years of compute for a steep discount. They're ideal for predictable, steady-state workloads. The footgun is buying inflexible Standard RIs when your needs might change.
Auto Scaling Groups: Elasticity and Self-Healing
An Auto Scaling Group (ASG) is like a thermostat for your servers, automatically adding or removing instances to match demand and replacing any that fail. Use it for web apps with variable traffic or services that need to self-heal from instance failures.
Cloud Load Balancer: Your App's Traffic Cop
A cloud load balancer is a traffic cop for your servers, distributing requests across a pool of machines to prevent overload. It's essential for scaling apps and ensuring high availability.
The Cloud's Shared Responsibility Model
Using the cloud means you share security duties with the provider. The split depends on the service: in IaaS, you manage the OS and up; in PaaS, just your app and data; in SaaS, mostly your data and users.
Cloud Regions and AZs: Infrastructure Built for Failure
Think of a cloud region as a city and its availability zones (AZs) as independent power grids. If one AZ fails, your app runs in another. The footgun is deploying to a single AZ; this provides no protection against data center-level outages.
High Availability: Designing Systems That Don't Go Down
High Availability (HA) means designing systems to survive failures by having redundant components ready to take over instantly. It's essential for services like payment gateways where downtime costs money and user trust.
Cloud Scalability vs. Elasticity: Planned Growth vs. Real-Time Reaction
Think of scalability as adding lanes to a highway for long-term growth. Elasticity is opening a reversible lane only during rush hour. Scalability handles predictable demand, like a product launch; elasticity manages unpredictable spikes, like a viral post.
CapEx vs. OpEx: The Cloud's Financial Shift
Cloud computing shifts IT spending from buying assets upfront (CapEx) to paying for services as you use them (OpEx). Think buying a car vs. hailing a ride. This model lets you scale on demand, but the biggest mistake is assuming it's always cheaper.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles