Intermediate everything in Cloud Platforms, page 5
OLAP Cube: Pre-Aggregating Data for Fast Analysis
An OLAP cube is like a Rubik's Cube for your data, pre-calculating answers to complex business questions. It powers BI tools, letting you 'slice and dice' sales data by region and time for fast reports. The footgun: data is typically stale, not real-time.
Lambda Architecture: Batch and Stream for Big Data
Lambda Architecture splits data into two paths: a slow, comprehensive batch layer and a fast, real-time stream layer. It's used in big data systems needing both historical accuracy and live views.
Apache Airflow: Code-Defined Data Pipelines
Airflow lets you define, schedule, and monitor complex data workflows as code, replacing brittle cron jobs. It's used for ETL jobs or ML training pipelines. The footgun is treating it as a data processing engine; it's an orchestrator, not the worker.
Dimensional Modeling: Facts vs. Dimensions
Dimensional modeling organizes data like a story: 'facts' are what happened (sales numbers) and 'dimensions' are the who, what, and where (customer, product). It's the foundation for data warehouses, turning raw data into analyzable BI reports.
Start/Stop Automation: Pay Only For What You Use
Start/stop automation is like putting your cloud resources on a timer to save money. It's essential for non-production environments like dev and staging used only during business hours.
Showback vs. Chargeback: Who Pays the Cloud Bill?
Showback shows teams their cloud costs for visibility; Chargeback makes them pay for it by moving costs to their budget. This helps control cloud spend by making engineers cost-aware. The footgun is treating Chargeback as inherently more mature than Showback.
FinOps Framework: Aligning Cloud Cost with Business Value
FinOps treats cloud spend as a business metric, not just an IT cost. It provides a shared framework for engineering, finance, and business to collaborate on data-driven spending decisions.
AWS Savings Plans: A Bulk Discount for Compute
Think of Savings Plans as a bulk discount for AWS compute. You commit to a consistent hourly spend for 1-3 years to get a lower rate on EC2, Fargate, and Lambda. The footgun is over-committing; you pay for your commitment even if you don't use.
Cloud Rightsizing: Stop Overpaying for VMs
Rightsizing stops you from overpaying for idle cloud capacity. It involves analyzing CPU and memory usage to shrink over-provisioned VMs. Always collaborate with application owners before making changes.
Cloud Cost Management: Taming Your Bill
Treat cloud spend like a utility bill you can actively control, not a fixed cost. It's essential when your AWS, GCP, or Azure bill is growing unpredictably. The biggest footgun is treating cost management as a one-time cleanup instead of a continuous process.
SLIs & SLOs: Measuring What Matters for Service Reliability
SLIs are what you measure (e.g., latency); SLOs are the target you aim for (e.g., 99% success). They replace vague feelings about service health with concrete numbers. This is how SREs define and manage reliability.
The Fan-out Pattern: One Message, Many Receivers
The fan-out pattern uses a single message to trigger multiple parallel actions, like a press conference where one announcement reaches many reporters. Use it for events like a new user signup that triggers emails, analytics, and fraud checks.
Idempotent Event Handlers: Don't Double-Count Events
An idempotent event handler ensures processing the same event multiple times has the same effect as processing it once. This is vital in event-driven systems to prevent data corruption from redelivered messages. The footgun is assuming exactly-once delivery.
AWS SAM: A Shorthand for Serverless on AWS
Think of AWS SAM as a developer-friendly shorthand for defining serverless applications. It simplifies creating Lambda functions and APIs by abstracting away verbose CloudFormation syntax, letting you build and test locally before deploying.
Kubernetes StatefulSet: Pods with Stable Identity
A StatefulSet gives Kubernetes pods a stable identity and dedicated storage, like assigning a permanent desk and locker to an employee. Use it for databases or clustered apps where nodes need to find each other and retain data across restarts.
Kubernetes Node: The Cluster's Worker Machine
A Kubernetes Node is a worker machine that runs your applications. Think of it as an employee receiving tasks (Pods) from the control plane manager. The common footgun is confusing the Node with the Pod; a Node is the server, while a Pod is the.
Kubernetes Control Plane: The Cluster's Brain
The Kubernetes control plane is the cluster's brain, making all global decisions like scheduling pods and responding to events. You interact with it via kubectl to manage your applications. The footgun: never run your own workloads on control plane nodes.
Promoting Code with Pipeline Stages
Think of pipeline stages as quality gates. Code must pass one gate, like 'build', before being promoted to the next, like 'deploy to staging'. This is core to CI/CD, moving code safely from dev to production. The footgun is making later stages less strict.
Rolling Updates: Deploying Code Without Downtime
A rolling update deploys new code by gradually replacing old application instances with new ones, ensuring zero downtime. It's the default for stateless services in orchestrators like Kubernetes.
AWS CodeDeploy: Automated, Safe Application Updates
AWS CodeDeploy automates pushing your application to servers, Lambda, or ECS. It handles complex updates across many targets, letting you release new features rapidly while minimizing downtime.
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