11–14 of 14 posts
Another option you might like is Flightcontrol[0]. It's similar to Porter, but newer and aims to make all the best AWS services as easy as PaaS. And unlike Porter, it doesn't charge more for horizontal and vertical scaling. Today, the server deployments use Fargate, and are truly hands off just like PaaS. Soon we're launching ECS+EC2 support which will let you customize the EC2 instance type, use GPUs, and leverage r…
Even on low-volume projects I've noticed reliability issues with Fly.io too. For example today we have requests timing out at the gateway (before hitting our services) while the status page indicates their current outage is only related to delayed app logs [0][1]. Haven't gone deep enough with the other new-ish PaaS providers (like Render and Railway) to get a feel for their limitations. Unless you're certain you nee…
I agree that Kubernetes is overkill, even at our scale. My biggest concern with "serverless" paradigms like Cloud Run or Fargate is with cold starts.
Even on low-volume projects I've noticed reliability issues with Fly.io too. For example today we have requests timing out at the gateway (before hitting our services) while the status page indicates their current outage is only related to delayed app logs [0][1]. Haven't gone deep enough with the other new-ish PaaS providers (like Render and Railway) to get a feel for their limitations. Unless you're certain you nee…
I agree that Kubernetes is overkill, even at our scale. My biggest concern with "serverless" paradigms like Cloud Run or Fargate is with cold starts.
Serverless functions spin up resources and run isolated code on-demand for every request as it's received. If you have no traffic, it scales down to zero and cold starts can be a concern. And paying for compute per-request like this can get very expensive at scale.
While Fargate is advertised as "serverless", I'd think of it as a fully container platform, it's closer to Heroku than it is serverless functions. You point it to an image, tell it how many instances you want to run, maybe set up some autoscaling rules (like to add more instances when CPU reaches X%), and then it'll run those instances 24/7. From what you've described, it sounds like a good fit.