Heroku: Core Impact
brandur.org
brandur.org
A few more people and we could've properly maintained the stacks. We should've had an entire team if not department dedicated to thinking about Docker. If I recall it was a part-time concern for like 2 of the language engineers (who had a ton of work on their plates).
Heroku should not have stopped at Cedar: it should've been the one to build something akin to k8s but with good DevEx.
As far as why we had headcount problems: it's because sfdc gave up on us. See Craig[0] and Adam[1]'s comments for more on that. We certainly did though: sfdc would have entire teams dedicated to similar roles we would have individuals handling part-time. Salesforce folks would tell you we were cocky assholes and they were right—but we also worked damn hard.
It's odd how whenever someone on HN mentions a list of cloud providers, they will list Google, IBM, and even Oracle before Microsoft Azure, which is the #2 biggest provider after Amazon.
It's like when a parent lists their children and just "forgets" their second child.
"Oh, we don't talk about Timmy..."
> So I can't fault Microsoft for Azure. I actually like it.
You literally do not hate microsoft more than the next guy
I use RDS on AWS because I'm doing some weird stuff that Render hosted Postgres can't handle, but nor can Heroku Postgres.
I cried when Periwinkle was leaked: that's when the writing was on the wall and even the most optimistic of us realized we were doomed.
I appreciate the community seems to care about our story so much.
When I worked at AWS, the thing I heard most frequently repeated in relation to security was "We don't want a front page of the NYT event." There's probably a good argument that AWS or Amazon would survive a "front page of the NYT" event (after all, we've seen Target etc do so), but the spirit of the phrase still resonates.
https://news.ycombinator.com/item?id=31356546
Which may be interesting since the Heroku conversation is hot right now.
NO! I always thought the very opposite.
Selling Heroku to Salesforce was a mistake.
Heroku should have cannibalized it's own dyno pricing and follow AWS Lambda with 100ms increments pricing. And after that do what Cloudflare is doing today.
Most likely any buyers would kill off/sunset most of it, and gain a lot of negativity. Not going to happen.
More likely is the rumours of it being rolled/rebranded/de-labelled into a Salesforce offering, and quietly sunset large chunks of it (which would be less noticeable than if any new buyers did so).
We're launching https://www.utopiops.com, a platform that can be replacement for Heroku on your own AWS.
We support ECS, EKS and static websites. We're working closely with our early users to tailor the services based on their specific requirements.
If anyone is interested in a demo, or a trial happy to provide more details.