441–450 of 590 posts
This is a sad day. Pricing changes are always hard, and having been through some of the earlier pricing changes at Heroku you can't make everyone happy. But, so many developers deployed their first app on Heroku and was a staple for so many bootcamps. Without it I'm confident we'd have less developers in the world. It is still one of the gold standards for developer experience. Years after its heyday companies and to…
Earlier quoted context omitted.
i belatedly came to this realization that this is a common problem for all hosting (CDNs, because free bandwidth, and CI/CD, because free compute, and anything that offers free storage) companies. I call this the PCN problem - free tier hosting for anything means you eventually have to deal with Porn, Crypto, Nazis. everyone handrolls prevention measures, i once proposed an industry council where we swap tips, but ev…
Only recently learned that crypto jerks will try to abuse free compute during the build step for hosting services
Earlier quoted context omitted.
Hetzner has dedicated server auctions for ~35 USD/mo. All are in EU datacenters though. https://www.hetzner.com/sb
What's a US data center equivalent? OVH? What's their lowest price for a dedicated server monthly?
Based on their current availability, US looks to be more in the neighborhood of $50 a month
Earlier quoted context omitted.
Second this — Heroku pg is the main reason I've stayed with them, paying $$$/month to host my service. If Fly (or Render) can match the seamlessness of that experience, that'll be where I host next.
Would it be OK if service like https://www.crunchydata.com was integrated with Fly?
Earlier quoted context omitted.
They're telling you why: having a free tier means allocating a lot of resources to fraud and abuse, which are rampant in hosting, especially now that you can convert hosting dollars almost directly to cash. It's a big problem, and I have every reason to believe they're being forthright about why they've made this decision.
OT: your HN profile says: > All comments Copyright © 2010, 2011, 2012, 2013, 2015, 2018, 2023, 2031 I'm curious. If you were to continue that sequence would the continuation be: A. 2044, 2065, 2099, 2154, 2242 B. 2044, 2065, 2099, 2154, 2243 C. Something else?
Earlier quoted context omitted.
It won't. It's a typical move from a business stuck in a death spiral, desperately searching for profits by blindly slashing expenses.
Is Heroku stuck in a death spiral? Source needed?
Heroku has two core tenets - developer experience and upgrade to paid tier for production workloads.
As a result, at least the Heroku customers I know use the free tier for a good portion of their _non_ customer-facing production workloads - prototypes, staging, administrative functions, and so on.
This both increases their cost and makes budget planning a lot less stable. It means developers may become motivated to start coming up with workflows that target other environments where they would normally target Heroku, which like robs Heroku of a source for future revenue. Once you take on the devops work yourself, Heroku is no longer price competitive.
In other words, this new cost makes the unique value of Heroku look quite a bit more like a detriment. Thats rather unfortunate.
Earlier quoted context omitted.
Presumably, "nazi" here is a stand-in for any form of communication not protected by free speech laws and / or is actively forbidden by government censors (or perhaps merely undesirable by social standards). Hate speech, anti-government advocacy, promotion of violence and terrorism etc will use "free" tier accounts because they want as little capability of being tracked to in-real-life people as possible. They may or…
Things like Kiwifarms which provide a risk of substantial reputational damage if you're seen to be supporting them. There's a campaign on Twitter to deplatform KF from Cloudflare after more SWATting incidents, for example.
Link to the public roadmap: https://github.com/orgs/heroku/projects/130 Blog post says "Salesforce has never been more focused on Heroku's future." but this looks like they are just keeping the lights on by deprecating and keeping security up to date. Which isn't bad if the product has reached maturity but I wonder if these really are the most important features users ask for. Why does the feedback link on the blog p…
We are doing more than keeping the lights on. Purpose of the public roadmap (which just launched, we'll need some time to really get it right, I'm sure) is to show what we are working on. Any comment on the work around github integration safety as an example? Watching for feedback here, but it's nice to know when I'm getting reachouts on product feedback directly who is touching base. Linked-in is great for that. But…
* HTTP/2 (3?) (on the roadmap) * a refresh of the dyno line-up - at least pass on some of the cost savings of removing/supporting free tier by reducing dyno pricing or preferably bumping specs * auto-scale for all dyno tiers * rebuild security team with reputable lead * edge / multi region active-active DX * edge ssl termination * iterate on chat ops (underrated feature) * more metrics * more alerting (e.g. crashed apps) * better user/access team management (default app roles) * enhanced secrets management in env (2 layers of env view/roles - config vs secrets) * DDOS protection * Treat CI env vars as secrets!
Earlier quoted context omitted.
They have money to invest. And so do other companies offering free products and yet they often vanish. Heroku is not new, they got investment ... maybe this whole cycle of free tier companies just isn't working?
> maybe this whole cycle of free tier companies just isn't working? That feels like a stretch. I can say for myself there are a number of developer services I pay for monthly that I don't think I would have tried if not for the free tier. Once you company starts stagnating (like Heroku) then sure, maybe it's time to kill the free tier since you aren't attracting people (other than scammers) but that's just a sign you…
Earlier quoted context omitted.
My big want here is containerized deployments with build + release steps to allow me to e.g. run migrations and after-deploy tasks (we use both). This prevented a move to Render for us previously.
Could you go into one more level of detail about your app? I think this will help me better understand content for some documentation. Here's the rough bits of what Fly has: 1. There's a release command ( https://fly.io/docs/reference/configuration/#run-one-off-com... ) that runs after the container is built, but before its deployed. In Rails that's when a database migration would be run. 2. To run a task after the a…
As far as the after-deployment tasks go, we automate those just like migrations - they're (occasionally very slow) one-offs that we don't want to hold up a restart for. Really, an analogue to the release command that can run after restart is all that I'm talking about here.