3 ms·
I'm no experienced Lambda user either, but here's a couple helpful things I've found: * I think API Gateway can throttle requests. Not sure if that was part of
by rockmeamedee 10y ago
I'm no experienced Lambda user either, but here's a couple helpful things I've found:
* I think API Gateway can throttle requests. Not sure if that was part of your pipeline or if your lambda had a different trigger.
* There is a Town clock SNS event https://alestic.com/2015/05/aws-lambda-recurring-schedule/ https://alestic.com/2015/05/aws-lambda-recurring-schedule/
- happyslobro 10y agoAh yes, I forgot about that. What I really needed from the clock was for it to somehow only trigger lambdas that actually had work to do. I didn't like the idea of them polling once per second per function, when 99℅ of the time, they would have nothing to do. I guess "town clock" was a mistake on my part.