Headless 360Intermediateload-testingperformancepeak
Plan load testing headless APIs before peak season
Real World Scenario
Last Black Friday crashed APIs at 3x normal traffic; leadership wants proof of readiness this year.
Expected Answer
• Model peak traffic from historical analytics plus growth factor
• Load test read (search) and write (checkout) paths independently
• Include auth token refresh load often forgotten
• Test from geographically distributed load generators
• Define pass criteria: p95 latency and error rate thresholds
• Coordinate with Salesforce on capacity planning if needed
• Game day runbook with rollback triggers
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Stay within limits by: Model peak traffic from historical analytics plus growth factor. Bulkify everything — never query or DML in loops. Include auth token refresh load often forgotten. Load test the critical path end-to-end—including payment webhooks—not isolated product GET. Balance speed of delivery with maintainability.
Architect Perspective
Load test the critical path end-to-end—including payment webhooks—not isolated product GET.