An enterprise compliance team needs to review 50,000 legal document summaries every night and have results ready by 8 AM. Each document is independent. Which approach best balances cost efficiency and reliability?

Question

Accepted Answer

B. Submit all 50,000 documents to the Batch API in the evening and poll for results before the team arrives in the morning. This is a textbook Batch API use case: high volume, independent requests, non-blocking (no one waits in real-time), with a known completion deadline (8 AM next morning). The overnight window comfortably accommodates the Batch API's 24-hour maximum, and the 50% cost savings at 50,000 documents are substantial. Option A is expensive at this scale. Option C requires infrastructure management for concurrency. Option D misrepresents the Batch API, which has no 1-hour SLA.

An enterprise compliance team needs to review 50,000 legal document summaries every night and have results ready by 8 AM. Each document is independent. Which approach best balances cost efficiency and reliability?

Related Questions

Discussion