A serverless API sees sudden bursts that overwhelm a relational database. Requests can be accepted asynchronously and processed within minutes. Which architecture best absorbs the burst?

1. Increase Lambda concurrency without a database capacity bound.
2. Buffer accepted work in SQS and bound worker concurrency to database capacity.
3. Retry every failed write immediately with no delay or queue.
4. Store accepted jobs only in API process memory.