← ☁️ Cloud Architecture
Core
Serverless retries and destinations: invocation modes and duplicate effects
Map Lambda invocation modes to retry ownership and failure capture. Design an idempotent event handler and distinguish asynchronous destinations from queue redrive behavior.
a free account opens the core tier · no card
RELATED CONCEPTS
PRACTICE THIS IN REAL QUESTIONS
Cloud Platforms & ArchitectureWhen is serverless the wrong choice? Talk me through cold starts and what they actually cost.→Platform Engineering & FinOpsWhere does serverless pricing actually bite, and when do functions beat VMs on cost?→Cloud Platforms & ArchitectureOne event fans out to ten thousand Lambda invocations and the payments API behind them falls over. What is going on?→Infrastructure as Code & ConfigurationHow does Ansible actually work? Explain inventory, playbooks, modules and why agentless matters.→Cloud Platforms & ArchitectureEC2, ECS, Fargate, EKS or Lambda: how do you choose where a service runs on AWS?→DevOps System Design & ArchitectureDesign a cron system that schedules two hundred thousand jobs across a shared fleet. What goes wrong at that scale?→