An e-commerce platform generates personalized product recommendation emails for users immediately after they complete a purchase. The engineering team considers using the Batch API to reduce costs. Is this appropriate?

Question

Accepted Answer

C. No — the customer's post-purchase experience depends on timely email delivery; the Batch API's unpredictable latency makes it unsuitable for this blocking workflow. The Batch API is inappropriate for any blocking workflow where users or downstream systems are waiting for results. A post-purchase email is time-sensitive — customers expect it promptly, and delays significantly degrade the experience. Because the Batch API has no SLA within its 24-hour window (results might arrive in minutes or hours), it cannot provide reliable timing for this use case. The 50% cost savings do not justify unpredictable delivery timing. The real-time API is correct for this scenario.

An e-commerce platform generates personalized product recommendation emails for users immediately after they complete a purchase. The engineering team considers using the Batch API to reduce costs. Is this appropriate?

Related Questions

Discussion