Q: A serverless payment gateway workflow occasionally takes up to 3 days to resolve because it waits heavily for manual human approval. Should you use AWS Step Functions Standard or Express Workflows?
You must undeniably use Standard Workflows.
#AWS #Cost & Architecture #L2 #Cloud #Infrastructure
🎙️ Candidate Opening & Architectural Context
""In a previous role, our monitoring paged me for a similar incident across our AWS VPC infrastructure. The interviewer is testing: Step Function workflow duration limits.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Advertisement
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
Initial Diagnostics & Root Cause Analysis
You must undeniably use Standard Workflows.
- Standard Workflows: Support extremely long-running, auditable executions that can pause and wait cleanly for up to 1 year. They are billed per transition, making them perfect for manual human approval steps and long-polling.
- Express Workflows: Are designed explicitly for massive, high-volume event processing (thousands per second). Their absolute maximum execution duration is capped violently at 5 minutes. They would time out instantly in this scenario.
2️⃣
Remediation & Permanent Safeguards
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Standard Workflows: Support extremely long-running, auditable executions that can pause and wait cleanly for up to 1 year. They ar."
⚡ 60-Second Elevator Pitch Talking Points
- Standard Workflows: Support extremely long-running, auditable executions that can pause and wait ...
- Express Workflows: Are designed explicitly for massive, high-volume event processing (thousands p...
Advertisement