This is a great article on how a serverless approach can reduce overhead for many applications. I’m still seeing them have a lot of cost in the API Gateway portion of the project, which caught me by surprise. Would this cost be less than standing up a simple web app that can accept incoming requests, and fire off the associated Lambda functions using the AWS SDK as the invocation event instead? We’ve had great luck with this approach at Backand, and have managed to reduce our costs even farther by relying upon a single EC2 instance that can dispatch calls to Lambda functions as appropriate - you could almost consider it a hybrid approach.
One other thing to look into would be to see if using a sole-provider serverless framework, as opposed to a combination of Serverless Framework for deployment and cloud formation management and API Gateway. The costs may be a little higher, but using some utilities they could potentially save on data transfer and API request costs by handing over a large portion of the management to a third party like Backand or Firebase. You’d still need a devops-oriented person to establish security schemes, but using this approach you’re able to outsource scaling, security, DB, and other functionality. I’ll grant it may not be economical at the OP’s scale, but for smaller projects looking to get spun up quickly it could be a valid alternative
This is a great article on how a serverless approach can reduce overhead for many applications. I’m still seeing them have a lot of cost in the API Gateway portion of the project, which caught me by surprise. Would this cost be less than standing up a simple web app that can accept incoming requests, and fire off the associated Lambda functions using the AWS SDK as the invocation event instead? We’ve had great luck with this approach at Backand, and have managed to reduce our costs even farther by relying upon a single EC2 instance that can dispatch calls to Lambda functions as appropriate - you could almost consider it a hybrid approach.
One other thing to look into would be to see if using a sole-provider serverless framework, as opposed to a combination of Serverless Framework for deployment and cloud formation management and API Gateway. The costs may be a little higher, but using some utilities they could potentially save on data transfer and API request costs by handing over a large portion of the management to a third party like Backand or Firebase. You’d still need a devops-oriented person to establish security schemes, but using this approach you’re able to outsource scaling, security, DB, and other functionality. I’ll grant it may not be economical at the OP’s scale, but for smaller projects looking to get spun up quickly it could be a valid alternative