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

301–310 of 366 posts

Re: An Update on Heroku

#301

Post by ghaff »

gonational wrote: post #254
Folcon wrote: post #241

Earlier quoted context omitted.

I'm just going to chime in here and say thank you, there still really isn't in my mind a comparable offering to heroku's git push and go straight to a reasonable production I honestly find it a bit nuts, there's offerings that come close, but using them I still get the impression that they've just not put in the time really refining that user interface, so I just wanted to say thank you for the work you and the GP di…

This! It absolutely boggles my mind that nothing else exists to fill this spot. Fly and others offer varying degrees of easier-than-AWS hosting, but nobody offers true PaaS like Heroku, IMHO.

The Heroku style of PaaS just isn't very interesting to most large businesses that actually pay for things. The world basically moved on to Kubernetes-based products (see Google and Red Hat)--or just shutdown like a lot of Cloud Foundry-based products. Yes, many individuals and smaller shops care more about simplicity but they're generally not willing/able to pay a lot (if anything).

Re: An Update on Heroku

#302

Post by acjohnson55 »

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.

I don't understand the dismissiveness. I think it's pretty clear. Keeping it going for the current users, but not trying to innovate. It might seem weird in an industry that prizes constant innovation and disruption, but this is a mature thing to do.

Re: An Update on Heroku

#303

Post by macintux »

brabel wrote: post #278
asenchi wrote: post #220

Earlier quoted context omitted.

It remains the greatest engineering team I've ever seen or had the pleasure to be a part of. I was only there from early 2011 to mid 2012 but what I took with me changed me as an engineer. The shear brilliance of the ideas and approaches...I was blessed to witness it. I don't think I can overstate it, though many will think this is all hyperbole. I didn't always agree with the decisions made and I was definitely ther…

> by 2012 we were drowning in tech debt and scaling challenges. > the greatest engineering team I've ever seen How do these two things reconcile in your opinion? In my view , doing something quickly is the easy part , good engineering is only needed exactly when you want things to be maintainable and scalable, so the assertions above don’t really make much sense to me.

In general, my impression has been that you don't want to architect your solution at first for massive scaling, because:

* You probably aren't going to need it, so putting the effort into scaling means slowing down your delivery of the very features that would make customers want your solution.

* It typically slows down performance of individual features.

* It definitely significant increases the complexity of your solution (and probably the user-facing tooling as well).

* It is difficult to achieve until you have the live traffic to test your approach.

Re: An Update on Heroku

#304

Post by hnmullany »

ryantgtg wrote: post #242
eek2121 wrote: post #183

Earlier quoted context omitted.

Most of my career, I've worked for startups and small/medium sized businesses, mostly using Ruby On Rails or Node based stuff for language/frameworks. In every single company I've worked for in the past 15-20 years in this capacity the biggest focus was to exit heroku as quickly as possible. The reason: Price. You don't get to charge a premium for tooling, especially not when open source tooling exists that lets you…

This is my experience, too. Heroku didn’t stay competitive price-wise with alternatives. And scaling even slightly from the basic dynos quadrupled (or whatever) the price. Feature and experience-wise, we were always really happy with heroku. I don’t know if this fits with the “salesforce purchased and let stagnate” narrative that nearly everyone here is pushing.

Heroku got a lot of attention and funding within Salesforce at least for the first few years - they grew from about $1M in ARR when they got acquired, and I think they peaked at around $200M (second hand - so I don't know if part of that was funny-money revenue allocated from Enterprise agreements.)

Re: An Update on Heroku

#305

Post by ghaff »

ptdorf wrote: post #219
Aurornis wrote: post #194

Earlier quoted context omitted.

Thanks for sharing your story. Those early days of using Heroku were really enjoyable for me. It felt so promising and simple. I remember explaining the concept to a lot of different people who didn't believe that the deployment model could be that simple and accessible until I showed them. Then life went on, I bounced around in my career, and forgot about Heroku. Years later I actually suggested it for someone to us…

The cancer of corporations: bureaucracy.

As corporations grow, they also increasingly need some level of process which can increasingly look a lot like bureaucracy.

Re: An Update on Heroku

#306

Post by whitepoplar »

asenchi wrote: post #220
bgentry wrote: post #187

As somebody whose first day working at Heroku was the day this acquisition closed, I think it’s mostly a misconception to blame Salesforce for Heroku’s stagnation and eventual irrelevance. Salesforce gave Heroku a ton of funding to build out a vision that was way ahead of its time. Docker didn’t even come out until 2013, AWS didn’t even have multiple regions when it was built. They mostly served as an investor and le…

It remains the greatest engineering team I've ever seen or had the pleasure to be a part of. I was only there from early 2011 to mid 2012 but what I took with me changed me as an engineer. The shear brilliance of the ideas and approaches...I was blessed to witness it. I don't think I can overstate it, though many will think this is all hyperbole. I didn't always agree with the decisions made and I was definitely ther…

Tell us more about some of these ideas and approaches that changed you as an engineer! We'd love to hear!

Re: An Update on Heroku

#307

Post by throwawaypath »

crashprone wrote: post #288
throwawaypath wrote: post #247

One of the worst "engineers" I've suffered working with (spent all day on Slack virtue signaling, put on a PIP) went to Heroku. A comment I made was "only a sinking ship would take them/her." This update from Heroku does not surprise me.

Comment adds nothing valuable to the discussion. Hope you at least feel better now.

Comment adds nothing valuable to the discussion. Hope you at least feel better now.

Re: An Update on Heroku

#308

Post by satvikpendem »

nextaccountic wrote: post #277
satvikpendem wrote: post #96

Earlier quoted context omitted.

If you like VPS, Hetzner with Dokploy. It works great, the UI has essentially all the features of Fly or Render that you'd use for deployment, like preview build URLs and environments.

Ok so I am researching what to use in this space - a Vercel-ish clone on cheap VPS - and, is Dokploy really the best option? What do you think about Caprover? https://github.com/caprover/caprover Or uh.. Dokku https://github.com/dokku/dokku Right now I am using Coolify but so far it has not been exactly reliable

I don't like their UIs, Dokploy's is far more modern. And yes Coolify is not known to be very reliable, especially because it's built on PHP.

Check out these videos:

https://youtu.be/ELkPcuO5ebo

https://youtu.be/RoANBROvUeE

Re: An Update on Heroku

#310

Post by barkerja »

CodinM wrote: post #151

As someone that migrated off of Heroku back in 2023 for a monitoring start-up - why were you still on Heroku?!

For us, the reason is we're primarily a Salesforce company and rely on the Heroku Connect product to facilitate bidirectional syncing between Salesforce and PostgreSQL (which also requires Heroku PG).

One of the biggest benefits to this product -- aside from the syncing mechanism -- is a bypass of Salesforce's extremely limiting (and expensive) API limits.

Post reply on HN