Learning/AWS SQS/29 — Hands-on Labs/Lab 08 — Batch APIs
Intermediate outline
This chapter is an outline. The curriculum, learning objectives and structure are settled; the prose, diagrams and code are still being written. What is below is the plan for the chapter, not the chapter.

Lab 08 — Batch APIs

Goal

Same throughput, one tenth the API calls — and a partial failure you have to handle.

Setup

To be written — CLI commands and an IaC equivalent for every resource, all prefixed sqs-course-.

Steps

  1. Send 1,000 messages one at a time; count the API calls
  2. Send 1,000 with SendMessageBatch; count again
  3. Receive with MaxNumberOfMessages = 1, then with 10; compare call counts
  4. Delete with DeleteMessageBatch; deliberately include one stale handle
  5. Inspect the Failed list in the response — note the HTTP status was 200
  6. Observe that receives often return fewer than 10 messages

What you should observe

  • A 10× reduction in API calls for identical work
  • Batch APIs return 200 with per-entry failures — the Failed list is not optional
  • You asked for up to 10; you got what was available

Why it happened

To be written — ties each observation back to the mechanism in 13 — Batch Processing.

Experiments to try

To be written — deliberate variations that change the outcome.

Teardown

To be written — every resource created above, in dependency order.

← Back to: 29 — Hands-on Labs