451–460 of 590 posts
https://blog.battlesnake.com/deploying-web-servers-for-free-...
It's really a shame, given how much we've relied on Heroku free tiers to lower barriers fr all.
Our community recently pulled together a guide for comparing different free hosting providers. https://blog.battlesnake.com/deploying-web-servers-for-free-... It's really a shame, given how much we've relied on Heroku free tiers to lower barriers fr all.
You might want to add a note regarding Railway's free plan:
"Render’s free database plan allows you to run a PostgreSQL database that automatically expires 90 days after creation" [0]
So it's more a trial than a free plan like Heroku's was (e.g., free forever under 10k rows)
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?
Salesforce doesn't need a free tier to generate product leads. They have an army of sales people to push the product to customers that will write them big fat checks, then hand down edicts from the CTO's office requiring their internal devs use the technology.
Fly.io has a dedicated process for moving off of Heroku. Auth via Heroku and they'll launch your app onto Fly. They also have a free tier. The process: https://fly.io/launch/heroku The docs: https://fly.io/docs/app-guides/speed-up-a-heroku-app I haven't used it [the Heroku -> Fly process] myself, but it's been around for quite some time!
Please let me know in the replies what you'd like to see at Fly that would make it as good, if not better, than Heroku. I recently started working at Fly to focus on making Rails & Ruby app deployments awesome, and of course Heroku set that benchmark almost a decade ago. I can't promise I'll get to everything, but I can promise that it will help me better prioritize what I should be focusing on to make Fly better for…
Earlier quoted context omitted.
> Competitors like Vercel don't just do what Heroku does, they do everything better. Vercel does not do, what Heroku does, besides a CDN, they do serverless functions. Correct me, if i'm wrong.
I mean Vercel has a lamdba/serverless feature but you can absolutely point a git repo at it and have it build your site and run your node backend. It's a little more abstracted away, but then again Heroku is just an abstraction on Aws, and the newer era of tools are a bit more abstract than Heroku.
I didn't know that, thanks.
Earlier quoted context omitted.
With some investment in infra as code we have a similar experience on aws. GitHub actions + terraform targeting ECS on fargate (pay for usage). Push to main build the container, pushes to elastic registry, makes the task/service, configures alba, etc.
Would you mind sharing how many working days went into building it? This was exactly what we tried to avoid with our (rather small) dev team.
It took our infra swe a few months to get MVP version working but he also did other infra related work at the same time. Complexity can change a lot depending on requirements, and ours are probably more stringent that Heroku ever supported. Because of sensitivity of the data we deal with there is now a relatively sophisticated identity management/permissioning/what-can-see-what-data component in how our infra is deployed which probably would not be the case for most companies. We also deploy ML models so there is additional issues with automation around keeping track of reproducability/provenance/ml pipeline regression/drift/deidentification/etc (which now a year later we haven't fully solved either!).
Earlier quoted context omitted.
Is Heroku stuck in a death spiral? Source needed?
No, this is about optimizing profitability. They were bought by Salesforce and that whole cohort (Salesforce, Oracle, et al) are machines optimized to extract as much money as possible from the Fortune 1000. Salesforce doesn't need a free tier to generate product leads. They have an army of sales people to push the product to customers that will write them big fat checks, then hand down edicts from the CTO's office r…
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…
Heroku are training wheels that never come off. I see an overall benefit to dev community, while painful initially, it will be a net-good for people to learn how to deploy an app on a bare metal server.
Earlier quoted context omitted.
As a CTO of a company which has a very similar situation - I can fully agree on that. We already started looking into a possible migration to another cloud provider. The biggest decision point would be a similar developer experience as with git push heroku master.
Would you mind elaborating on what does the "similar developer experience as with git push heroku master" mean for you? I'm a founder at https://stacktape.com , and we're trying to provide full power of AWS with a developer-friendly experience, similar to Heroku or serverless framework. Even after doing a ton of research, I'm still not 100% sure which of the Heroku's features are the killer features that the competin…
My gut feeling from reading your homepage is that you're automating a lot of AWS service deployments on my behalf, but not "obfuscating" it that much from me either.
Your pricing talks about "Resources" which I assume are either AWS services or instances of those services. The free plan says that a REST api needs 40 resources which seems... like a lot? Is 40 good? bad? :-)
Heroku specifically allows you to think of your app == 1 dyno (depending on how much you scale it obviously), not 40 services.
I also note that the $290/month team plan talks about unlimited resources but doesn't specify their size/capacity. Heroku has sort of t-shirt sized tiers for dynos (and addons as well, like Postgres). What size of resources are you deploying on my behalf?
I do see the value of what you're doing, I'm just not getting a "as easy as Heroku" feeling. It seems potentially more powerful, but also raw-er i.e. this is automated AWS (that I might need to care for / understand), not... "git push heroku master" :-)
Can anyone clarify what the minimum cost of say, a demo Django project would be now? I come up with $16/month, using a $7 dyno and a $9 postgres instance. Is that accurate? Also, if you're testing the deployment process, what's the minimum charge? Say I push a project, test it to see that the deployment worked, and then destroy the project in less than three minutes. Will I be charged for three minutes of resources,…
Yeah, that's accurate. If you need a worker (like celery), then that's another $7, as that's an extra dyno. If you need redis, then that will be another $15.
> Also, if you're testing the deployment process, what's the minimum charge? Say I push a project, test it to see that the deployment worked, and then destroy the project in less than three minutes. Will I be charged for three minutes of resources, or is there some hourly/daily/monthly minimum? I can't find that kind of info anywhere.
They charge you per minute (or per second?) iirc.