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

101–110 of 366 posts

Re: An Update on Heroku

#101

Post by bityard »

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.

In a company I used to work for, "sustaining engineering" was the team of developers that handled all of the bugs and issues reported by customers on old-but-still-technically-supported versions of the products. (The ones who worked on current versions of the products where just "engineering.")

So basically heroku will fix whatever is broken, but don't expect any new features or development.

Re: An Update on Heroku

#103

Post by realkf »

bobbyiliev wrote: post #86

I've been using DigitalOcean App Platform for a while now. It's not a 1:1 Heroku replacement, but the git-based deploys, managed DBs, and ability to move to Droplets later without a big migration have worked very well for me.

Yeah, I moved a while back to DO's App Platform. I've not had any issues with them so far. Recommend them a lot.

Re: An Update on Heroku

#104

Post by o_m »

bearjaws wrote: post #88

The downfall of Heroku should be studied, they had lightning in a bottle and blew it. Salesforce acquired them and just let it die, baffling.

What is there to be studied? Once a company is acquired you bounce. There is usually a two year grace period before you start feeling the pain as a customer, which should give you the time to migrate.

Re: An Update on Heroku

#105

Post by anamexis »

o_m wrote: post #104
bearjaws wrote: post #88

The downfall of Heroku should be studied, they had lightning in a bottle and blew it. Salesforce acquired them and just let it die, baffling.

What is there to be studied? Once a company is acquired you bounce. There is usually a two year grace period before you start feeling the pain as a customer, which should give you the time to migrate.

Salesforce acquired Heroku 15 years ago.

Re: An Update on Heroku

#106

Post by awestroke »

earless1 wrote: post #36
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.

From a business perspective, this means they will not be investing in innovation on the platform anymore. Instead, they will focus their efforts on maintaining the current operations and keeping the lights on.

As opposed to the relentless innovation they have demonstrated in the past 5+ years? /s

Re: An Update on Heroku

#107

Post by ezekg »

decidertm wrote: post #84
ezekg wrote: post #83

Earlier quoted context omitted.

Do you have any public docs on how y'all migrate customers out of Heroku Postgres without downtime? Seems to be the sticking point for a lot of people, myself included.

hey! northflank supports the same buildpacks that you run on Heroku, so it should be fairly straightforward. we have these docs for a more detailed walkthrough: 1/ https://northflank.com/docs/v1/application/migrate-from-hero... 2/ https://northflank.com/blog/how-to-migrate-from-heroku-a-ste...

Sorry, but telling people to take a logical backup of their database, and then download it onto their local work station is insane for a production application. First, a logical backup at any decent scale will fail, and second, I don't even have enough local storage to do that -- even ignoring the compliance issues with downloading a full copy of production data onto a work station.

For a company like Northflank, I'd expect actual production-grade documentation for migrating, not instructions that are only applicable to a toy app.

Re: An Update on Heroku

#108

Post by carimura »

anamexis wrote: post #105
o_m wrote: post #104

Earlier quoted context omitted.

What is there to be studied? Once a company is acquired you bounce. There is usually a two year grace period before you start feeling the pain as a customer, which should give you the time to migrate.

Salesforce acquired Heroku 15 years ago.

Time flies. I do think the vision lasted pretty long post acquisition, maybe 5 years or so, but then the inevitable seemed... inevitable.

Re: An Update on Heroku

#110

Post by danudey »

ceejayoz wrote: post #78
throwoutway wrote: post #57

Earlier quoted context omitted.

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".

The lights will stay on until they burn out or the power goes off, or someone bumps the light switch or steals the light bulbs.
Post reply on HN