Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

An Update on Heroku

heroku.com

Post reply on HN
Print view View original

71–80 of 366 posts

Re: An Update on Heroku

#71

Post by quentindanjou »

nightpool wrote: post #23
quentindanjou wrote: post #14

Earlier quoted context omitted.

Railway for backend APIs. Render for front-end apps. That's my current go-to. Although I would consider, _when possible_, using Vercel or Netlify.

Why/when do you use Railway over Render?

When bandwidth matters, when you don't want to over or under provision, when you need multiple seats: if you make a project with a small team, Render is going to be quite expensive because of the cost of each seat while Railway offers unlimited seats for they paid plans. Just the whole pricing is different, I found myself more leaning into Railway when doing calculations.

Re: An Update on Heroku

#72

Post by Trasmatta »

petcat wrote: post #30
simonw wrote: post #7

I wonder how much money Salesforce would need to sell what's left of Heroku to a better steward.

My understanding is that Heroku is just an AWS reseller. I don't know if there's a lot of value in a PaaS piggy-backing on another PaaS anymore. Especially for Salesforce.

I don't see AWS as a PaaS at all. Heroku's selling point has always been how it makes everything way easier.

Re: An Update on Heroku

#73

Post by pelagicAustral »

I used to be a fan of Heroku when I started working web apps... The deployments were so easy, but I became numb to the actual task of dealing with the complexities of a deployment, when they killed the free tier I struggled for a while... I work with Rails, and I used to bitch a lot about how hard it was to deploy an app, but in retrospective I kind of thank Salesforce for murdering their own product.

Now I deploy at my leisure with stuff like Dokku, or Kamal, directly on a 5 bucks VM on a fresh Linux box in 10 minutes flat. I wrote a nice web app that wraps around Dokku and manage the stack much in the same way I did before with Heroku... I'm much happier and I learned a ton on the way.

Re: An Update on Heroku

#75

Post by simonw »

petcat wrote: post #30
simonw wrote: post #7

I wonder how much money Salesforce would need to sell what's left of Heroku to a better steward.

My understanding is that Heroku is just an AWS reseller. I don't know if there's a lot of value in a PaaS piggy-backing on another PaaS anymore. Especially for Salesforce.

There's a ton of value right now in the existing customers. None of them want to put effort into migrating away from Heroku if they can avoid it.

Re: An Update on Heroku

#76

Post by swat535 »

kuczmama wrote: post #48

This is a sad day. I used heroku for years (in the past). A few alternatives to consider - https://render.com/ - this is very close to heroku - https://coolify.io/ - My personal favorite. It's slightly more involved, but you can run it on any hardware like hetzner and save a boatload.

How does render compare to fly.io? Does anyone has experience running production rails apps on these?

Re: An Update on Heroku

#77

Post by hoherd »

singularity2001 wrote: post #59

It's a bit surprising, one would have thought that with the event of accessible coding through agents, such site deployment sites would prosper.

Didn't you read the last line of the announcement? They have enterprise AI dollars to chase! Salesforce wants some of them billions. Gotta make up for the 42% their stock price has dipped in the last 12 months.

Re: An Update on Heroku

#78

Post by ceejayoz »

throwoutway wrote: post #57
g8oz wrote: post #5

"transitioning to a sustaining engineering model". I don't care what anyone says, it takes real talent to come up with lines like this.

Could have just said we will Keep the Lights on

This reads more like "we won't deliberately turn the lights off… but they're probably gonna break on their own eventually".

Re: An Update on Heroku

#79

Post by loloquwowndueo »

nightpool wrote: post #11
sebiw wrote: post #8

> helping organizations build and deploy enterprise-grade AI in a secure and trusted way > Enterprise Account contracts will no longer be offered to new customers Seems contradictory or I just don't understand how they do product management. My opinion: Heroku had its time but then stagnated heavily in keeping up with what was going on around it. With the rise of Container as a Service platforms there now were a mult…

Translation: We're going to reassign the engineers into Salesforce AI.

I thought if you were all in on AI you wouldn’t need engineers - just swarms of agents doing everything. :)

Re: An Update on Heroku

#80

Post by jbm »

nelsonfigueroa wrote: post #45

The corporate speak is crazy. I think the update boils down to this sentence: > Enterprise Account contracts will no longer be offered to new customers

Yeah I agree. I saw someone say that they were not in KTLO mode, but this seems pretty bad, especially considering it happening at Salesforce.
Post reply on HN