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.
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.
> 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?
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.
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
If Heroku works for you, that is good. Ignore my comment.
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.
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.
https://www.linkedin.com/feed/update/urn:li:activity:7267639...
Why would you bother with Heroku?
GCP isn't well seen in that regard.
Pretty sure you can't build an ASP.NET Core app in Visual Basic.NET (as it lacks support for some modern language features the framework needs).
F# is on the same spot, hence why I nowadays say CLR has changed meaning to C# Language Runtime, the whole mantra of Common Language Runtime and Common Language Specification compliant libraries are now gone.
F# at least is officially supported for ASP.NET Core, and has official ASP.NET Core templates in Visual Studio.
then k8s happened. deis workflows adopts k8s but it's never finished. deis team acquired by Microsoft not long after iirc.
Also see https://devcenter.heroku.com/articles/dotnet-heroku-support-...
.NET is the only (cross-platform) server runtime anyone should consider running Server Apps on.
Both scale to zero, are portable, and allow full use of your language/runtime/framework of choice. Take any app you are deploying to instance compute today and add a Dockerfile and ship it.
AWS App runner comes close, but doesn't have the option to scale to zero.
I wish they had maintained momentum and attempted to price competitively, but at this point its probably too late.
