apprunner-roadmap VS postgres-ha

Examples for products in this category are: Google Cloud Run, AWS App Runner, Azure Container Apps. Each has different scalability, cost, and integration trade-offs.

The deployment failed, and there were no logs available to help me debug the issue. There's an open issue on GitHub that has been around for over a year, but there doesn't seem to be a solution in sight.

If you're looking for something simple, that you can onboard to relatively quickly, that doesn't require a lot of oversight, consider App Runner, https://aws.amazon.com/apprunner/. EKS and Kubernetes are extremely powerful and flexible, but they come a fair amount of complexity. If you don't care about the orchestrator (or running your application in another cloud), try App Runner.

The reader will learn how to create a web application firewall with AWS WAF and AWS App Runner as a web application. AWS App Runner is an AWS service that deploys web applications or API using Amazon ECR or GitHub only. While AWS WAF (Web Application Firewall) is an AWS service that can protect the web application.

Yes, exactly. That's the problem. I found the issue here.

I wonder what the aversion is to using a plain old server / vps. It's really not that difficult to deploy nowadays [0][1][2][3] and I'd rather get an $8 bill every month as insurance than ever worry about shit like OP just went through. It'll probably be more performant anyway due to cold starts and "edge" still having to hit us-east-1 for data.. cache your static files with Cloud Flare/Front. People are always surprised by how much traffic a single VPS can take[4] and believe it all has to be serverless to be web scale. I believe HN still runs on a single core or something.

There's a ton of places to get cloud credits as well, too many to link, so just Bing™ it

[0] https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_...

[1] https://aws.amazon.com/apprunner/

[2] https://cloud.google.com/run

[3] https://render.com/

[4] https://news.ycombinator.com/item?id=34676186

AWS AppRunner could do more or less everything. You'd have to build a container image yourself, since AppRunner does not have C++ support for the "Code-based" service, but building a container really isn't more complex than installing that bare metal server. (Really, pick an OS, install dependencies, copy your code, start a service. That is all.)

App Runner

Fly Postgres is just a Fly.io app. You can see the source code for it right here:

https://github.com/fly-apps/postgres-ha

It has some direct `flyctl` integration (which is also open source), but it's not doing anything you can't do yourself if you want.

We do not! You have full administrative access to your postgres. You can create offsite replicas, or even fork the Postgres app we use and deploy over your Fly.io installed postgres: https://github.com/fly-apps/postgres-ha

RDS preventing external streaming replicas is the most annoying thing ever.

Our Postgres is not an RDS replacement. Lots of devs use RDS with Fly. In fact, Postgres on Fly is just a normal Fly app: https://github.com/fly-apps/postgres-ha

Ultimately, we think devs are better off if managed database services come from companies who specialize in those DBs. First party managed DBs trend towards mediocre, all the interesting Postgres features come from Heroku/Crunchy/Timescale/Supabase.

So we're "saving" managed Postgres for one of those folks. For the most part, they're more interested in giving AWS money because very large potential customers do. At some point, though, we'll be big enough to be attractive to DB companies.

Our postgres clusters are just a Fly app: https://github.com/fly-apps/postgres-ha

You could run your own PG by modifying that app. Right now we're calling it "automated" and not managed, though. All alerts about health and other issues go straight to customers, we don't have DBAs that will touch these things yet.