I switched from the Serverless Framework to AWS-CDK 5 years ago
<a href="https://aws.amazon.com/cdk/" rel="nofollow">https://aws.amazon.com/cdk/</a><p>I use the Javascript library of aws-cdk
Related discussion: <a href="https://news.ycombinator.com/item?id=40589152">https://news.ycombinator.com/item?id=40589152</a>
Can you briefly explain what you think the issues are? I'm just moving from azure functions over to lambda. Code will likely be dotnet and I just assumed I'd use the aws provided tools: codecommit/build/pipeline/deploy. Azure devops did the job fine last time.
Vercel / Next has them built into the framework these days. You just write a function and it deploys automagically with the rest of the frontend. I think they use Cloudflare Workers for that instead of AWS...? Not sure.<p><a href="https://vercel.com/docs/functions" rel="nofollow">https://vercel.com/docs/functions</a>
I've been using AWS CDK which now supports go. The only gotcha is that I have to cleanup the build cache occasionally which can easily build up-to several gigs over time.
My business has about a dozen lambdas that I configure using terraform, and to deploy I use a regular CI service with the AWS CLI installed.<p>Been working great for about 3.5 years now
We’re building <a href="https://rx.run" rel="nofollow">https://rx.run</a> so you don’t have to think about these sorts of things and can just ship your app.<p>If you can write a function, you can deploy to the cloud. No infra or deployments to configure or manage. Storage, auth, payments, and more are all built right in.<p>Currently in beta and TypeScript only but support for all mainstream languages coming soon.