A meter-event consumer invokes Lambda once per SQS message, wasting per-invoke overhead. How should processing be optimized?
Select an answer to reveal the explanation.
Short Explanation
One Lambda wake-up per tiny meter tick pays the cold-start tax over and over. Bump the SQS batch size so one invoke chews through a handful of events. Less overhead, better cost and latency for the stream.
Full Explanation
SQS event sources for Lambda support batching so multiple messages are delivered per invocation, amortizing runtime overhead for high-volume meter events. Forcing batch size one maximizes overhead; removing the queue or disabling careful failure handling does not optimize throughput. Appropriate batch sizes are a standard messaging optimization.