amazon web services - AWS Pub/Sub Message Pattern -


can explain me advantage or disadvantage of using sns -> lambda vs. sns -> sqs -> lambda.

i'm looking setup architecture pub/sub micro-service messaging, having queue in front of every lambda seems excessive.

unless has changed, question of whether makes more sense deploy sns → lambda, or sns → sqs → lambda, based on premise significant flaw.

as indicated in supported event sources in lambda documentation, lambda events can sourced s3, dynamodb, kinesis, sns, ses, cognito, cloudformation, cloudwatch & events (including scheduled events), aws config, amazon echo, , api gateway.

and, of course, can invoke them directly.

but sqs not supported lambda event source.


Comments