4 ms·
One key takeaway here is that in a typical serverless API setup, the AWS API Gateway will actually end up costing more than the Lambda compute. According to the
by markonen 9y ago
One key takeaway here is that in a typical serverless API setup, the AWS API Gateway will actually end up costing more than the Lambda compute. According to the breakdown in this post the Mercury Web Parser API isn't an exception.
I don't want to be the guy saying that 39 million requests isn't a lot, but especially if your API serves trivial responses to a lot more requests, API Gateway can end up being the opposite of cheap.
- nikon 9y agoAgreed that the API Gateway is overpriced, but what is your alternative - build a Lambda that somehow is your API gateway?
- markonen 9y agoThere is no truly serverless alternative, although since the API for invoking Lambda functions synchronously is free, you can possibly roll your own API Gateway (assuming you are OK with having servers for that). But my point was more about simply being cognizant of the API Gateway cost. Too many Serverless tutorials/testimonials assume no significant request volume and end up ignoring this aspect of AWS billing.
- vidarh 9y agoThe genius of AWS lies in a pricing structure that is easy to get approval for, and where developers once they've started using it are rarely aware of how much it costs... I see so many cases where people are bewildered at how they've come to spend as much as they do because nobody understands the cost model.
- michaelbuckbee 9y agoThis is very much one of those YMMV (quite wildly depending on the project) but one option might be to write the files to S3. You can configure a Lambda to run for each new file written, and then get the result back into a separate bucket.
- tjholowaychuk 9y agoLambda itself is already ~300% more expensive than EC2, but in comparison API Gateway is indeed much much more than Lambda for processing the requests.