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.
That sounds right to me though I always deploy my nextJS projects on a VPS, so it just transforms them behind the scenes to the equivalent of self hosted node hosted "lambdas" - only without the associated more aggressive timeouts around Vercel unless you're a paying customer.
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.
We’re building https://rx.run so you don’t have to think about these sorts of things and can just ship your app.
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.
Currently in beta and TypeScript only but support for all mainstream languages coming soon.
I wanted to expand and say that if you are keen on writing and managing infra and running it yourself, besides Serverless Framework, SST, CDK, arc.codes, and Terraform are all good options.
SAM is probably my favorite way to do it myself. Easy enough to wrap your function up however you please and it automatically handles zipping for me. Can even do layers for my dependencies.
[1]: https://github.com/aws/chalice
[2]: https://www.signalstalk.com/
[3]: https://www.ycverify.com/
[4]: https://www.airexif.com/