Massively Parallel SQS Processing
Benn Linger

Instead of writing to SQS, what about simply invoking the Lambda with a type of ‘Event’(which is async and is simply queued for you, presumably via SQS)?

The primary downside I see here is you don’t have a say in how many consumers you have(whereas with your approach, you control this number directly via # of SNS topics. The upsides are simplicity, and cost(you’re only paying for S3 and Lambda)

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.