3 ms·
I'm excited for this. This replaces what I wanted to use SQS for. SQS always felt like too much vendor lock-in to me to justify not using something like RabbitM
by debaserab2 12y ago
I'm excited for this. This replaces what I wanted to use SQS for.
SQS always felt like too much vendor lock-in to me to justify not using something like RabbitMQ or Beanstalkd.
With Lambda, the resource consuming the queue is managed for me - that is huge. Also, the pay by time model is perfect for this - instead of managing when to stop/start resource intensive instances, I don't even have to think about the problem. I only get charged what I used, which can be crucial during growth stages of a business or prototype.
The big penalty is the vendor lock-in, but this tips the scales for me for certain things.
- crescentfresh 12y ago> *the resource consuming the queue Are you referring to kinesis as the queue here? Sqs/sns are not (yet?) supported as event generators for lambda.