Hacker News Reader

Comment by dec0dedab0de | Hacker News Reader

Heroku seemed like it was going to be the future back then. Every time I find myself struggling to understand some nonsense in Azure I dream of the simpler future we lost.

View on HN

They got painfully expensive and then acquired. I still remember the arguments with clients and finally went all in AWS ECS, which is still quite pricey but clients seem to complain less about the Amazon bill then they did about Heroku.

Other than the pricing, for something built for simplicity, i always found their config method bit weird. Maybe it's just me b/c I first learned the aws stack, and got tired of managing EKS

Fly.io brings back some of that easy of deploy.

Yep, agreed. Fly.io is the closest to Heroku that I’ve found.

Caprover for me, but fly.io is pretty cool, reminds me of flynn.io

Especially the pricing is equally joyous.

Sucks that it didn't become that. "heroku up" or "cf push" (Heroku kind of sort of invented build packs) was hella addictive.

Shoot, I'm sad that Docker didn't become the way to run containers. compose/swarm is still light years easier than Kubernetes

I guess Heroku ran so that Vercel could fly?

Yeah I don't see a reason to use k8s if not on cloud, and k8s on cloud is even more complex. Compose is still the right size for one box, that one command does all was really nice to have

Give Cloud Run a try if you haven't. It's basically serverless done right.

Azure Container Apps is very similar to Cloud Run if you can't use GCP

I tried to use this the other day and found out they still don’t support arm64 :(

Somehow ECS does though… tradeoffs everywhere I look have made me dizzy.

I've got to give credit where it is due... It really feels like Laravel Cloud picked up where Heroku left off. Or at least is trying to.

Reply on news.ycombinator.com