After all the chatter this week, I've come to the conclusion that Heroku froze at the perfect time for my 4 person company. All of these so called "features" are exactly what we don't want or need. 1. Multi-region deployment only work if your database is globally distributed too. However, making your database globally distributed creates a set of new problems, most of which take time away from your core business. 2.…
Fly.io: The reclaimer of Heroku's magic
91–100 of 320 posts
Re: Fly.io: The reclaimer of Heroku's magic
#92Can someone explain what fly.io actually is for someone with an AWS background?
Re: Fly.io: The reclaimer of Heroku's magic
#93Earlier quoted context omitted.
They aren’t charging for the certificate so much as they’re charging for TLS termination, infrastructure, DNS, caching, handling invalidations, etc. It’s also 10 free then $0.10/mo per certificate thereafter (or $2/mo for wildcard). They also donate 50% of their TLS fees to Let’s Encrypt. So, yes, some users will have have to pay for certificates, but it seems extremely reasonable to me.
well, maybe but, my expectation as a PaaS customer in 2022 is that you shouldn't need to pay for a SSL cert the expectation is because nobody else charges for them anymore, not even their competitors
* Render.com charges $0.60 per custom domain after the first 25
* Heroku gives you "free" custom certificates once you're on a $7/mo minimum.
Re: Fly.io: The reclaimer of Heroku's magic
#94The main thing I want is pipelines - review apps, staging apps, and promotion to production, all integrated closely with GitHub, along with a slack integration that lets me do all of it in a public chatroom. Until another service has all of this, we’re sticking with Heroku.
I get the intention with Slack. I’ve never understood, except for the geek cred, pushing work into chat services. Github is open to the team too. I hear complaints about chat distractions and see engineers create those distractions. I’m at a loss why we want to do that to ourselves? Nevermind it’s one more pipeline for messages to lost in. It’s needless complexity and configuration too.
Re: Fly.io: The reclaimer of Heroku's magic
#95Earlier quoted context omitted.
Even small companies should be multi-region, if they care about uptime.
No, they shouldn't. In many instances it's cheaper to tolerate downtime than to pay to avoid it, especially when there's no SLA involved.
Re: Fly.io: The reclaimer of Heroku's magic
#96Re: Fly.io: The reclaimer of Heroku's magic
#97Earlier quoted context omitted.
well, maybe but, my expectation as a PaaS customer in 2022 is that you shouldn't need to pay for a SSL cert the expectation is because nobody else charges for them anymore, not even their competitors
Do they? I feel like you're just uncomfortable with line-item pricing and prefer flat all-in-one pricing. What are the other competitors that offer actual PaaS instead of static-site hosting? * Render.com charges $0.60 per custom domain after the first 25 * Heroku gives you "free" custom certificates once you're on a $7/mo minimum.
Re: Fly.io: The reclaimer of Heroku's magic
#98Earlier quoted context omitted.
I've got a small amount of dynamic content
DigitalOcean App Platform has a $5/month flat rate for dynamic stuff on top of two static sites hosted for free... if something goes crazy and you end up using a wild amount of outbound data, it looks like the next jump up is only to $12
Re: Fly.io: The reclaimer of Heroku's magic
#99Being a small-scale Heroku user, I have a hard time deciding whether to stay with Heroku or move to render.com or fly.io. Before the latest incident, Heroku seemed to be frozen but stable. Now… I don't know. Are they even trying to bring back Github Connect? Fly.io seems cutting-edge but I feel I would not profit from their multi-region, close to the user infrastructure. So what are their tradeoffs? Render.com appear…
Review apps on Render are called Preview Environments: https://render.com/docs/preview-environments
Re: Fly.io: The reclaimer of Heroku's magic
#100After all the chatter this week, I've come to the conclusion that Heroku froze at the perfect time for my 4 person company. All of these so called "features" are exactly what we don't want or need. 1. Multi-region deployment only work if your database is globally distributed too. However, making your database globally distributed creates a set of new problems, most of which take time away from your core business. 2.…
Hot take: if people spent half the energy doing multi-region that they today spend screwing around with Kubernetes, they’d be a hell of a lot more reliable.
For larger teams having a well defined API that delineates applications from infrastructure that doesn't require extreme specialist knowledge (it still requires some specialist knowledge but vastly less than direct manipulation of resources via something like Terraform) is a massive productivity boost.
Of course none of that matters if you have 4 developers like OP but for folks like myself that routinely end up at places with 300+ engineers then it's a huge deal.