[filestorage]

Frontend: Angular or Vue, deployed on AWS S3 bucket + cloudfront (for https)

Backend: AWS Appsync (or AWS API Gateway) integrated with AWS Lambdas written in Golang. Authentication through AWS Cognito. DB: anything serverless from AWS (Dynamodb, Aurora etc.)

This way the app would be 100% serverless, no need for effort to scale it or to maintain the infrastructure (apart from automating the ifrastructure through AWS CDK).

[mattrighetti]

You won’t need a lot of effort to scale even with a Go backend deployed on an EC2 instance in the majority of cases.

Serverless is cool when you start with 300 users and you’re still in the free tier plan. After that, it’s going to cost you a fortune when you really need to scale, and I’m not even thinking about the time that you would need to waste writing everything back to a monolith/microservice, because that is what’s going to happen most likely.

[definitelyauser]

I wrote a Go application to run on AWS lambda, but also compileable as a monolith.

Was fun running on lamba etc, until as you say, the costs starts soaring massively. Moved it to a cheap VPS and never looked back.