[nemothekid]

I don't think it's that hard to a learn a little bit of AWS. What my "default" is

1. Host the complete React/Vue/static site of choice on netlify

2. Host the backend on AWS. I used to use ECS+Fargate, which means you just create a docker container, open some ports, and git push, but now it's even easier with AWS AppRunner. If you didn't want to touch AWS (it gets hairy fast), I would use something like PlanetScale or CockroachDB which have generous free tiers. From there you have a github action to push your container to your AWS ECR and AppRunner automatically redeploys your app. The only other platform that I think comes close to "I have my code just host it, and make sure it's redundant" is Fly.io

[southerntofu]

> I don't think it's that hard to a learn a little bit of AWS.

It's a lot more complicated than anything reasonable about deploying a webapp. Any shared hosting solution or deployment platform (think fly/shuttle) will be cheaper and easier to reason about. Even selfhosting on a rented VM or dedicated server and configuring auto-updates and maintenance windows will be much easier.

By going to netlify/AWS you are now tying the destiny of your app to two megacorps, doubling the risk of downtime (and cloud uptime is certainly not as good as dedicated) and other bugs.

[nemothekid]

Have you used AppRunner? I'm not talking about using AWS RDS, EC2 setting up IAM profiles or anything. AppRunner is fairly new and it's, IMO, simpler than Fly.io for webapps. Likewise, I don't think renting a VM or dedicated server is an option if you just want to deploy your app - if you don't want to think about deployment, networking, SSL provisioning, or failover and just your business logic, the appeal of Fly.io, netlify and Apprunner is just having an endpoint where you can 'git push' and having those platforms take care of everything.