Looks like it's still up and running, not sure that qualifies as a failure
Why did Heroku fail?
91–100 of 161 posts
Re: Why did Heroku fail?
#92Looks like it's still up and running, not sure that qualifies as a failure
I remember when you just git pushed to heroku and your stuff magically was a working deploy.
Later there was docker and after setting up your CI/CD you had almost the same heroku experience with half of the costs.
As deployment became easier there was no need for heroku. Is was killed by Docker.
Yeah you still can use it. But sure it's pricey...
Re: Why did Heroku fail?
#93Only thing heroku fail at was not becoming more cheap but other than it's good as it gets
Re: Why did Heroku fail?
#94Earlier quoted context omitted.
I can see this argument but at the same time Dockerfiles for my preferred framework (Phoenix) are more or less muscle memory for me at this point. The better question is: why don't frameworks come with a Dockerfile by default? The effort:reward ratio on containerization is huge, it gives you your app in a runnable, dependency-free format that you can build reliably and deploy on an extremely diverse set of platforms.
Dependency free? Isn’t Docker a dependency itself? And it’s the most annoying one — no other dependency constantly keeps a core going at 15% on my machine, or considers not upgrading a premium feature, or incessantly interrupts my work with NPS pop ups even when I’m doing nothing related to Docker. If anyone at Docker is reading this, I mark “100% no” when you interrupt me with pop up asking if I’d recommend your pro…
Docker Desktop is a development dependency, but you can also use Podman or minikube. I just use Podman these days, I prefer it. The container format is all standard these days, you don’t actually need anything Docker to use it. Fargate and Fly don’t even actually run the container directly, they convert it to a VM with Firecracker first.
Re: Why did Heroku fail?
#95Current paying Heroku customer, so... feels successful enough to me!
Re: Why did Heroku fail?
#96Does Matz still work at Heroku?
Re: Why did Heroku fail?
#97> Containers (introduced in 2013) also changed DevOps and software deployment landscape. Yet, container-native PaaS (e.g., OpenShift) also failed.
If being in every Fortune 100 company running some of the world's largest containerized platforms in production is failure, I want to fail like that
Re: Why did Heroku fail?
#98Earlier quoted context omitted.
It’s a preview of all big fish:small fish acquisitions really. There are some notable exceptions, but for the most part you should assume that an acquisition of a product you use will eventually mean you’ll need to go elsewhere imo.
Acquisitions always ruin the thing being acquired.
Instagram seems ok.
Re: Why did Heroku fail?
#99Did Heroku fail? Heroku was the biggest in a long line of developer tools. The PaaS and now FaaS models are still alive and well. A lot of developers want them. I know people are hot on containers and k8s but devs, who need to focus on code and business logic, have poorer productivity when they have to shift into thinking about ops. Heroku inspired a lot including direct competitors (like Cloud Foundry). A lot of mon…
> Heroku inspired a lot including direct competitors (like Cloud Foundry). A lot of money has been made and people jobs make easier. Ah Cloud Foundry. Something I drink to forget. CF was the tool Salesforce should've bought or written. Heroku not so much.
Was it so bad? My experience with it was resoundingly positive, and saw lots of productivity gains with a great developer experience for teams that could build apps with strong guard rails in place.
Now everyone and the kitchen sink „needs“ their own kubernetes cluster and operations teams struggle to build complex landing zones for the underlying cloud infrastructure so teams don’t shoot their own foot off all too easily…
Re: Why did Heroku fail?
#100As someone that put a good portion of their working career into helping create Heroku alongside many others, several who contributed way more and had a larger impact, the notion that it failed is probably the first thing that should be up for debate. But because we seem to want to debate this on a weekly basis... Heroku made reproducible builds and deployments a thing at a time people were used to ssh'ing in and scp'…
Exactly, it was a massive success. I never used Heroku but it was an great concept and a huge achievement.
After an acquisition products normally fail as large companies are too sclerotic to adopt or even value new ways of working, so they just destroy what they don’t understand, often after paying a huge premium for it.