Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

After reading the description of AWS Lambda, I expected SQS to be first in the list of event sources. Huh.



Wouldn't that be kind of unnecessary, when it's not too tough to write an SQS-reactive client?

Starting with S3 fills a gap as there is AFAIK otherwise no way to start processing based on changes to S3, without writing a rather wasteful program to list the resources, maintain state, and hunt for differences.


But if you have an SQS reactive client it would sit in EC2. With a service like Lambda, they are promising millisecond based pricing. A very ambitious project by them.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: