4 ms·
Very nice. The previously recommended implementation, IIRC, involved having a lambda basically polling SQS and invoking other lambdas to handle the messages. Ve
by ralusek 8y ago
Very nice. The previously recommended implementation, IIRC, involved having a lambda basically polling SQS and invoking other lambdas to handle the messages. Very clunky. It's weird, because SQS as an event source is probably the first service you would have expected this behavior out of. Not that I'm complaining, better late than never.
On an unrelated note, does anybody else think that there is a very large/poorly defined behavioral umbrella shared by SQS, Kinesis, and Amazon MQ?
- leetbulb 8y agoSQS is just a simple message queue: messages queue up and once consumed, they're gone. Kinesis is more like Kafka, being durable and replayable. Amazon MQ is just hosted ActiveMQ. All three have different use cases.