3 ms·

Awesome thanks! Sorry to bug but this is very interesting to me. Did you use a framework like Serverless?

scarface74 7y ago
No. I’m of the belief that when you choose a platform, go all in. Given a choice between the Serverless platform and AWS’s Serverless Application Model, I would choose SAM. I also work for a company that pays for the business support plan, they will help you to an extent with any weirdness in their own platform - but not with third party utilities. Another advantage with using SAM, is that you can create and configure your lambda/API Gateway from the web console and then export your SAM/CloudFormation template. All that being said, for APIs, I don’t use either. I would recommend using standard frameworks like C#/WebAPI, JS/Node, Python/Flask/Django instead and using the proxy integration libraries that AWS provides. It lets you develop/debug locally like you are accustom to and it gives you the optionality to move your APIs to Fargate (Serverless Docker) or EC2 instances without any code changes: 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... Node: https://github.com/awslabs/aws-serverless-express https://github.com/awslabs/aws-serverless-express Python/Flask https://dev.to/apcelent/deploying-flask-on-aws-lambda-4k42 https://dev.to/apcelent/deploying-flask-on-aws-lambda-4k42 I’ve been told that there are similar frameworks for other languages but those are the three that I use. If you have any other questions, feel free to email me. My address is in my profile. I’m not a consultant trying to sell anything....
- nickthemagicman 7y ago
  Thanks so much! This is really interesting. I think acloud.guru has a similar set up and they pay basically nothing for their millions of QPS. Going to research this more for my next project.

No. I’m of the belief that when you choose a platform, go all in. Given a choice between the Serverless platform and AWS’s Serverless Application Model, I would choose SAM. I also work for a company that pays for the business support plan, they will help you to an extent with any weirdness in their own platform - but not with third party utilities. Another advantage with using SAM, is that you can create and configure your lambda/API Gateway from the web console and then export your SAM/CloudFormation template. All that being said, for APIs, I don’t use either. I would recommend using standard frameworks like C#/WebAPI, JS/Node, Python/Flask/Django instead and using the proxy integration libraries that AWS provides. It lets you develop/debug locally like you are accustom to and it gives you the optionality to move your APIs to Fargate (Serverless Docker) or EC2 instances without any code changes: 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... Node: https://github.com/awslabs/aws-serverless-express https://github.com/awslabs/aws-serverless-express Python/Flask https://dev.to/apcelent/deploying-flask-on-aws-lambda-4k42 https://dev.to/apcelent/deploying-flask-on-aws-lambda-4k42 I’ve been told that there are similar frameworks for other languages but those are the three that I use. If you have any other questions, feel free to email me. My address is in my profile. I’m not a consultant trying to sell anything....

nickthemagicman 7y ago
Thanks so much! This is really interesting. I think acloud.guru has a similar set up and they pay basically nothing for their millions of QPS. Going to research this more for my next project.