[rtpg]

Heroku is still probably the platform that offers the most well built-out "here's all your operational needs for the first N years of your business" system, without causing you to have to deal with a billion concepts.

I have found Heroku to be going downhill a lot, but after moving away from it I often feel a bit of regret from this decision. You get _so much_ operational niceness out of the box with Heroku.

[runesoerensen]

We’ve been working the next generation of Heroku - and actually also launching that this week! Check out our post on it here https://blog.heroku.com/planting-new-platform-roots-cloud-na...

[jrochkind1]

It is encouraging to see that heroku is actually working on rolling new things out -- for a bit it hasn't clear if it was just in frozen "squeezing all the juice out with as little investment as possible" mode forever.

I'm having trouble interpreting that blog post to understand what it might actually mean for me or if I'd want to use it or what advantages it would have, looking forward to learning more.

[thanksgiving]

Really glad to read there is a local story.

> Today, OCI images are the new cloud executables. By moving to OCI artifacts, all Fir apps will be using images with compatibility across different environments. This means you can build your application once, run it locally, and deploy it anywhere, without worrying about vendor lock-in or compatibility issues.

Is this something I can try out locally without signing up for heroku first?

[runesoerensen]

Yep you can use our CNBs anywhere! More info and instructions here: https://github.com/heroku/buildpacks

[paxys]

Marketing speak aside, I'm curious what is actually changing for the end developer in the "next generation". Heroku already supports building and deploying containers, and that will presumably continue.

[schneems]

One big part that I'm personally excited about is support for Cloud Native Buildpacks. It's an open spec, part of the CNCF, and produces container images. You can use it to debug locally and can try it out now https://github.com/heroku/buildpacks/blob/main/docs/ruby/REA....

To go along with that we've built and maintain a Rust framework for writing CNBs https://github.com/heroku/libcnb.rs. I maintain the Ruby CNB and so I'm pretty excited to see some of my stuff in action.

> Heroku already supports building and deploying containers

Kinda. Heroku created a container ecosystem before OCI images were a thing. Apps deployed to the current Cedar infrastructure are deployed as "slugs" basically a tgz of the application directory that's loaded onto an LXC container, and unzipped to run on a base image (also called a stack) https://devcenter.heroku.com/articles/slug-compiler.

One big benefit of moving towards a standards compliant future instead of homebrew, is that customers also have access to that ecosystem. That's what enables things like being able to run and debug application images locally. It's the standards and community. We went fast and blazed some trails, now we're aiming to "go far," together with the community.

[chaz6]

I am pleased to see support for OpenTelemetry on the way. As a heavy user of AWS Lambda, the observability provided by X-Ray is invaluable for troubleshooting and improving performance.

[emilsedgh]

We've been on Heroku Enterprise for 8 years now. I read your comment and clicked on the link with so much enthusiasm.

Duh. You guys have completely forgotten who your audience is. Your audience is _application developers_. I have no idea what all that mambo jambo means in that article _and thats why I pay Heroku_.

I'm on Heroku because I don't want to know about cloud native and fir and open telemtry are. You tell me I should get excited on Heroku? How about improving your autoscaling options so the narrow response-time-based scaling is not the only option?

All that article tells me is that you guys are maybe improving your underlying infrastructure. Meh. Good for you. From a customer (AKA Application Developer) perspective nothing has changed.

[schneems]

The blog post is one of three published recently. It's from Terence Lee, an architect and former maintainer of Bundler (Ruby package manager). He co-founded the Cloud Native Buildpack project and was part of open sourcing the original Ruby buildpack. He gets pretty into the weeds with the tech.

The other article that's not been linked yet is this one https://blog.heroku.com/next-generation-heroku-platform. It's still not exactly what you're asking for "give me the application features" but it is a little less lingo heavy.

One thing kinda hidden in there:

> and AWS Graviton into the platform.

That means ARM support. Already the Heroku supported buildpacks work with both AMD (x86) and ARM (aarch64). Think mac Intel versus M(1/2/3/4) chips.

> From a customer (AKA Application Developer) perspective

I posted another comment earlier. Local debugging with CNBs is pretty neat. But I also agree, I see this still as an "investment" phase. This is the start of the work, that gets us more fun stuff later.

> How about improving your autoscaling options so the narrow response-time-based scaling is not the only option?

This is not my team, so I'm speaking not from first-hand experience. It's my understanding that Kubernetes has a pretty rich ecosystem for autoscaling. On our current platform, if someone wants to try out an autoscaler, it's a bespoke solution and difficult to try in the wild. Moving to a more standards based and community backed infrastructure means what's easy to do on Kubernetes, should also be easy for us to do on Heroku on the new platform.

I hear that you care about autoscaling options and I'll pass that along. Anything specific in that area?

[baconlorem]

You all really are living in the future, says it was last updated tomorrow XD

[lmm]

/r/usdefaultism. It was already December 3rd in most of the world when you posted.

[baconlorem]

I had considered that, time is hard

I guess I was assuming it was computed, not manually entered, therefore it's the most trivial of bugs, and was just trying to have some fun with a bug report

[lmm]

Even if it was computed, the only reasonable interpretation of a date given without a timezone (either explicitly or implicitly from the location) is that it's in UTC.

[cglee]

15 years on Heroku, absolutely no regrets and would do it again and again and again. It's one of those "no one goes there because it's too busy" type of situations. Don't fall for the noise, just use Heroku and move on with your life.

[czhu12]

Same thing happened to us. Moved to kubernetes 2 years and we had to rebuild all the features of Heroku in house against a kubernetes backend.

I’ve been working in my spare time to try to create an open source version of this, in case it would be useful to anyone else in the future https://github.com/czhu12/canine

[wqtz]

I geniunely and strongly believe PaaS and BaaS do not have a sustainable business model for the long term. Most of the platforms are losing money for each user they onboard. No matter how "loved" a platform is they are not actually making money and some point they are going to "get you". All the new platforms are constantly raising money to compensate for the costs and nobody is actually engineering solutions to reduce cost but doing feature engineering that is actually increasing their cost per user.

If Heroku works for you, that is good. Ignore my comment.

[tmpz22]

PaaS is just a middleman service providing convenience over more bare bones infrastructure. Look at the entire world of profitable middleman companies and you’ll see there’s plenty of viability in the business model, but it’s not as easy as a golden goose.

[rtpg]

> Most of the platforms are losing money for each user they onboard.

I really don't think they're losing money on onboarding, but I can totally see an argument for the fixed costs being so high that it doesn't work out.

[theanonymousone]

I used these so called "build packs" a lot and owe Heroku a great deal in general.

However, when I was "forced to" use Docker containers instead of custom build packs (Heroku also supports them), I didn't look back: It's a non-vendor-locked, portable, industry standard, which works with every framework of my choice, not just Django and Spring Boot. It also doesn't need an extra effort to support.Net, or anything else for that matter.

[schneems]

Cloud Native Buildpacks now produce OCI images. Here’s a tutorial for using them locally https://github.com/heroku/buildpacks/blob/main/docs/ruby/REA...

[theanonymousone]

Yes. I mentioned that Heroku also supports them.

[schneems]

There’s a difference between classic “buildpacks” and “cloud native buildpacks” today you cannot use “cloud native buildpacks” on Heroku, but you can sign up for our pilot platform called Fir that will support them.

The “classic” buildpacks cannot natively produce docker images but CNBs can https://devcenter.heroku.com/articles/buildpacks.

[cjonas]

I imagine what it could have been if it wasn't acquired by Salesforce and it makes me sad