In 2017 we went under a feature freeze and no new features were allowed to be worked on. Anyone can look at the Heroku Changelog to verify this yourself (of course features that were in progress still rolled out over some of 2018). We had tons of attrition (without backfill) and even a layoff afterwards. Heroku is probably 1/3 of what it was at its peak around 2014.
SFDC gave up on us because we wanted to build a developer platform and they wanted us to build an enterprise platform. We sucked at enterprise features so they gave us the axe.
It's like this all the way. Postgres is one click on Heroku, a miniature ordeal on GAE. Yeah I can handle it, but why. Maybe I don't have the patience and there's some light at the end of the tunnel. I thought maybe that light was gRPC, but turns out App Engine ironically can't run gRPC services.
$ cd
$ echo "one"
one
$ echo "two"
two
$ echo "three"
three
$ history | tail -3
10089 cd
10090 echo "one"
10091 echo "three"
When you remember to do it, that is.We were able to support _hundreds_ of applications, scale up at a moment's notice (applications were _very_ spiky traffic) and we didn't need a single member of infrastructure staff. We had engineers with _some_ backend-heavy knowledge, but nobody who could really get in to the guts of an infrastructure problem.
We charged Heroku out at cost to customers on top of our daily rate and it's barely a rounding error except for the largest of projects.
Don't get me wrong, the overall issue is that Heroku just isn't actively maintained anymore and that's going to put off new customers (as it should), but for those heavily invested in the platform right now, cost is not a factor that will be pushing them away.
Was written by the person you are responding to.
Possibly the most clearly and simply CF-based is from Swisscom:
https://www.swisscom.ch/en/business/enterprise/offer/cloud/c...
Even there, i see no links to getting started docs, or pricing.
Launching laravel app on heroku is magic, git push and done. On render and fly.io? Man I hope you don't suck at Docker cause it took me forever.
Render.com seems to be the closest. It's gotten a lot closer in the past two years. And is basically trying to be more or less a clone of heroku, with a few minor update tweaks for how the world has changed (while heroku has not).
Maybe it'll reach it before heroku fully implodes -- although it's hard because so much of heroku is also the ecosystem, that so many third-parties are adding value to heroku too, from add-ons, to just writing documentation for how to integrate their thing with heroku, to external non-approved "add-ons". (If the hirefire.io developer is reading this... hirefire for render?)
Fly.io is also really interesting -- for trying to do something different than heroku, actually much more sophisticated/interesting than heroku, but the trade-off is that it's not really as management-free as heroku, it has seemed to me. (I don't want to write a Dockerfile, nope). But maybe it'll get closer too.
Biggest differentiator with me and the rest? They focus on "look you can git push to deploy, we're just like Heroku!" while I am all about this DevEx.
So like parent OP said about what is comparable is my goals too.
I hope my product and vision of being "What if we rebuilt Heroku on today's tools with the DevEx?"
You can learn more and sign up for beta at https://primcloud.com
Made up reasons... to support the ponzi scheme of devops to increase salaries
I get your frustration but have to disagree; solutions like k8s exists because users, (often internal users mind you), expect things like rollouts of features several times a day, horizontal scalability etc.
I know there's a mantra on HN of let's go back to how things were in '95 and in some ways I'd love that but it just doesn't seem possible. You have to remember most devs just want to get their tickets done, they don't want to make anything complex if they can avoid it.
That being said if there's certain trends, (hardly set by your average developer), you have to go with at least some of it if you want to remain 'marketable' unfortunately.
Most developers also don't think they're working at the next Google. There's a different group within many software companies that likes to think so, usually not your ICs.
Most developers also don't think they're working
at the next Google. There's a different group within
many software companies that likes to think so, usually
not your ICs.
In the past ten years, I've worked at three companies with dozens of developers.I don't know if they "think they're working at the next Google", but I would say they have close to literally no conception of "performance" that doesn't mean "scaling out" to hilariously overcomplicated architectures that serve mainly to pump metric tons of money into AWS' coffers.
I worked at a company that thought you needed a Redis cluster because Performance Reasons. And they paid AWS handsomely for that belief.
What were we storing in Redis, you ask? Literally kilobytes of ephemeral data (cached values, etc).
A cluster. For kilobytes.
Obviously most examples aren't that nutty, but this kind of thinking has poisoned a whole generation of developers. It's not their money, so who cares about the AWS bill? Fuck hunting for missing indexes in the database, they just spin up a new server. It makes them look better to management because they're "getting things done" and management isn't tech-savvy enough to know otherwise.
And these aren't morons. These are talented people who are also kicking legitimate butt in many cases.
Docker images are a way for people to run anything they want on Fly.io. You probably won't need them on one of our happy path frameworks.
It's true that Heroku has a better experience, but that doesn't matter if the NRE for making it work on a cheaper platform is recouped after barely a month. I think the fact that these services are able to be successful despite having a worse experience shows how uncompetitive Heroku's pricing is.
If you've tried Render without Docker and it still took you forever, that's a bug we'd love to fix if you can email me (in profile).
All it requires is a Procfile, which can contain a single line telling how to start your server and that you can extend to add other process types. It's not even needed for simple apps.
> cmd: python helloworld.py
doesn't seem massively less complicated than
FROM alpine CMD ["python", "helloworld.py"]
FWIW, I've never used heroku in production so maybe it's more about the constraints of heroku than the number of words, but it just doesn't seem like a huge deal to me.
The smallest one I've used was probably a screen full, due to updating packages, setting up bundler paths, etc. A production dockerfile is much larger with non-root user shenanigans, etc.
But to answer your question about Heroku, a Procfile is much smaller and more constrained in scope than a Dockerfile.
Not single line, but two lines, sure. Though you're at the mercy of your upstream image and how it configures things. Though I guess that's also true of buildpacks.
Plenty of my Dockerfiles are no more than a couple lines.
Heroku was still nicer in most ways of course, at least in my opinion.
A Procfile works well with what you'd want to do on Heroku: run a webserver, and maybe run some other worker process. It's a single line per process, equivalent to what you run locally.
To compare it to one of their current competitors, render [1], for something with all the same features as gave me that $100/mo figure, you're looking at about $15/mo.
1. There are now comparable competitors that are cheaper.
2. They seem to have stopped maintaining it properly which is gradually leading a loss of trust.
This combined with something like Doku gives one a sense of what could be possible.
I've been a happy Hetzner customer for years, BUT
1) They are cheap because they are comparable to a discount supermarket chain
2) They are not a cloud platform
2.1) They offer none of the advanced features available on modern cloud platforms
2.2) It would be almost impossible to build a PaaS like Heroku on Hetzner infrastructure
3) The latency to anywhere outside Europe is pretty bad (regarding EU data centers) and their network is not the best (regarding the whole network)
4) The cheap dedicated server offerings are consumer hardware (and possibly thus are the hosts for the cloud services), and the more expensive server hardware offerings are not necessarily cheaper than other options
5) They have consistent issues with their virtual/cloud offerings that are not remediable due to the aforementioned lack of advanced PaaS functionality
There is much more going on behind the scenes of a platform like Heroku than a single dokku instance on a budget host. You are comparing single apples to a global distribution chain of bananas.
We too use some Hetzner servers at work for infrequently accessed databases that have no need to be highly available. We recently migrated non-production logging to a Hetzner dedicated with 8TB of HDD. Almost unbeatable price.
Choose the right tool for the job. I have nothing against Hetzner, but I’ve been seeing them mentioned dozens of times in unsuitable contexts by now.
To put that in context, I've been a (mostly happy) architect on all three major clouds for several years. The thing that "triggered" me to explore alternative options is GCP's continuing pricing increases across the board, and it's extremely bad pricing model for indie projects (that used to NOT be the case).
One thing to realize though is all of this is VERY relative - reliability etc. CAN be achieved by using proper primitives (Kubernetes etc.), but that comes at the cost of additional setup. That does however has its upsides too, meaning that these days pretty much everything under the sun can be done via K8s on bare metal, and migrated later somewhere else with relative ease.
I've always held the opinion that the markup on GCP, AWS, etc, is more than remediated by the savings in manpower requirement and cost of maintaining your own infrastructure.
Don't get me wrong, I love playing with self-hosted k8s for non-production, but when it comes to production, there's no real room for mistakes, downtime, constant maintenance and whatsoever.
If I had the time, or we had a dedicated SRE, sure - that might be a good path forward - but only if there is the chance of outgrowing the cost/profit ratio at some point. Unfortunately, what we provide at work is not a public offering, yet at the same time its being used by institutional money and has to have phenomenal availability and stability - I'd be hard pressed to sign off on a move to anything else in that case..
The problem is, big enterprise is "all in" on K8s and that becomes hard to reason about because when I tell them "use all of the optimizations available via GKE" they bark that that "ties them to GCP". But then when I wear another hat (as I did above) and suggest the opposite, folks in the other camp say we shouldn't rely on self- or semi-self-managed options. It seems there's no "win" here :-)
Also, to put in context what I meant above re recent price increases on GCP:
1) Per-cluster fee when it used to be free. This hurts hobbyist projects in particular (and yes, I know about the free tier for one zonal cluster, but that's not enough for playing around with one prod and one dev cluster env...).
2) Regional VM to multi-regional bucket traffic when it used to be free. This one is a huge degradation - used to be one of the selling points for Google's "Global Network", and there appears to be no excuse for it other than money-making, as Corey[0] famously mentioned. This hurts us in particular because we process so much data that this matters - right now, our (already exorbitant) cloud bill is a time bomb that is expected to go up on the scale of 50% or some such. Yeah :-)
Despite charging a lot even for internal traffic, AWS never increased pricing for any of their products, as far as I know (indeed, they decrease it over time..). That says something about GCP's reputation - it's a problem unique to Google Cloud, afaik. It breaks the fundamental trust in the platform.
[0] https://www.lastweekinaws.com/blog/google-cloud-alters-the-d...
I'm building a product that intends to bridge that gap[0] -- but I think it should be done in a way that works for any provider. There are so many other smaller providers out there with decent prices, but that are completely missing the services.
It's been getting better recently though! Aiven also just raised a bunch of money, so maybe we'll see a decoupling of services from the same to multiple clouds as they expand as well.
[0]: https://nimbusws.com
Had they become more competitive in terms of pricing, a large, large chunk of companies would've used them rather than moving to solutions like Kube, etc, or a bunch of Heroku clones which are now taking off as it's being considered a "Sinking Ship".
Just see this:
https://blog.porter.run/why-companies-move-off-heroku/
The reasons they are suggesting [that companies leave Heroku for] (besides the costs) are a bunch of non-reasons and small nuisances. The main reason is the cost, and the cost issue will become bigger and bigger of an issue as competing solutions get cheaper and cheaper, until Heroku is completely sunk and abandoned.
We are still using Heroku and I really hope they would fix the pricing before we bite the bullet and just spend a couple of weeks moving to a cheaper alternative. There's no vendor lock in on 12 Factor Apps you see.