Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Day 85 - 88 suggestion: AWS Lambda and API Gateway Limits #11

Closed
ericchou1 opened this issue Jun 1, 2019 · 1 comment
Closed

Day 85 - 88 suggestion: AWS Lambda and API Gateway Limits #11

ericchou1 opened this issue Jun 1, 2019 · 1 comment
Assignees

Comments

@ericchou1
Copy link
Contributor

I am a big fan of API Gateway + Lambda and have been using it for a while (for example, this blog, https://www.twilio.com/blog/2017/06/build-serverless-api-amazon-web-services-api-gateway.html). But we have hit a few limitations on both Lambda (https://docs.aws.amazon.com/lambda/latest/dg/limits.html) and API Gateway (https://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html) as we scale up our services. For lambda, the deployment size limit restricts the libraries we can include; and the API key limit on API Gateway limits the number of unique keys we can distribute per region.

Azure Functions and Azure API Management and GCP equivalents, on the other hand, are more relaxed.

Not promoting one cloud or the other, but if I were to think about deployment today, I would definitely take the limitation on each service into consideration. So wonder if you'd like to make a note or two in the README or what not.

@bbelderbos bbelderbos self-assigned this Jun 8, 2019
@ericchou1
Copy link
Contributor Author

Close issue as this is a suggestion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants