4 ms·

If you figure out let me know ;) no solution is without drawbacks!

• scarface74 7y ago
  Maybe it increases the load time of the lambda? But I’m already using a lambda attached to a VPC using the proxy integration and running either Node/Express or C#/Web API so its not like I’m always using lambda as efficiently and lightweight as possible. So there’s that...
  • aledalgrande 7y ago
    Mm are you using Lambda as a sort of router? The linked project is developed by Amazon and it translates into native Lambda layers. If they did their job with performance (which I trust Amazon devs to do), there should be no difference.
    • scarface74 7y ago
      When you use proxy integration all requests go directly to your lambda instead of using API Gateway for routing and translation. The lambda integration translates the request into something your framework understands. Node/Express: https://github.com/awslabs/aws-serverless-express https://github.com/awslabs/aws-serverless-express C#/Web API: https://aws.amazon.com/blogs/developer/deploy-an-existing-asp-net-core-web-api-to-aws-lambda/ https://aws.amazon.com/blogs/developer/deploy-an-existing-as... Python/Flask: https://pypi.org/project/flask-lambda-support/ https://pypi.org/project/flask-lambda-support/