Live data from Hacker News

Migrating our backend from Vercel to Fly.io

openstatus.dev

81–90 of 160 posts

Re: Migrating our backend from Vercel to Fly.io

#81
post #58

I’m curious if you looked at Heroku (I work there). You mention functions (which we don’t support), also servers (which we definitely support). I’m curious if that’s it or there was more to the decision.

I’m a bit out of the loop but I thought heroku died or is languishing under Salesforce. That’s my current perception of everything and no longer see it recommended in HN threads. Hopefully this does not come off as an attack (it’s not).

It never stopped working, it just... stopped. More of an omen than a practical issue (so far)

Re: Migrating our backend from Vercel to Fly.io

#82
post #43

TLDR: They could have done it cheaper, quicker and without adding DevOps to their workload with just migrating to Cloudflare. - Vercel: 150$/m. - Fly: 23$/m ( + managing servers and devops) - Cloudflare: 11 $/m. --- (original comment) They could have gone from Vercel to Cloudflare to reduce their costs. But that would have been almost no work to create a blog post about :p https://developers.cloudflare.com/pages/fram…

Can you deploy 700MB Dockerfiles to Cloudflare, as they mention as a minimum requirement in the article?

Didn't they only need the 700MB dockerfile due to Fly.io requiring it?

Re: Migrating our backend from Vercel to Fly.io

#83
post #30

Earlier quoted context omitted.

I worked at ZEIT (before it became Vercel) and if they've retained even a 10th of their engineering culture then they're solid, if not a bit "niche" in what and who they target. Anecdotal, sure, but it'd be hard to quantify it.

It’s funny how frontend has a stigma of less serious engineering when the caliber of programming being done at Vercel is far beyond the level of inadequacy I’ve seen being in big tech FAANG eng departments.

'use server'

sql("select * from db");

This is what Vercel is pushing into React code. The caliber of their work is low, very low. They are con masters with MBAs

Re: Migrating our backend from Vercel to Fly.io

#85

Earlier quoted context omitted.

It’s funny how frontend has a stigma of less serious engineering when the caliber of programming being done at Vercel is far beyond the level of inadequacy I’ve seen being in big tech FAANG eng departments.

'use server' sql("select * from db"); This is what Vercel is pushing into React code. The caliber of their work is low, very low. They are con masters with MBAs

That's awesome work. You don't like it for aesthetic reasons, pre-conceptions of aesthetic purity. That's fine too and I think I agree. But it's awesome work.

Re: Migrating our backend from Vercel to Fly.io

#86
post #3

> Edge functions are cost-effective as you only pay for the actual CPU execution. > We have over 1000 monitors, and the monthly cost to run them would be $150. > While on fly we only have 6 servers with 2vcpu/512Mb It cost us $23.34 monthly ($3.89*6). So edge functions are in no way cost-effective right? People using lambda functions are getting ripped off, they could just buy a couple of VPS.

In what universe is the difference between $23/mo and some amount less than that incomparable? That's what? Two paid users worth of revenue? $23 per month is a rounding error. It's one T-shirt. It's the cost of a few minutes of your time. If you're running a business and you're worried about saving ones of dollars on hosting, you need to reconsider how you're spending your time and how your business makes money.

unless you remove the need for said server then you save on reduced complexity/maintenance which is money

Re: Migrating our backend from Vercel to Fly.io

#87
post #56

Earlier quoted context omitted.

> I really don’t understand how people can trust platforms like Vercel It's not an apples to apples choice. The people who use Vercel don't know anything about how to deploy on AWS. That's the whole point of Vercel. Whether or not they can be trusted is really orthogonal to the reason they were selected as a provider. But that said, they're just a layer over AWS so why should they be significantly less trustworthy? I…

> The people who use Vercel don't know anything about how to deploy on AWS Ehhhh. I’ve been deploying to AWS professionally for years and I’d choose Vercel for a personal project any day of the week. Life’s too short to play devops/sysadmin/sre without someone paying you the big bucks.

This. Anyone who has done enough ops knows that a platform (Vercel, Heroku, Netlify etc) which lets devs connect a git repo with a couple of clicks, and deploys automatically happen is a good devops experience.

This is great for personal projects. This is great for budding projects in a professional setup as well.

Re: Migrating our backend from Vercel to Fly.io

#88

Earlier quoted context omitted.

'use server' sql("select * from db"); This is what Vercel is pushing into React code. The caliber of their work is low, very low. They are con masters with MBAs

That's awesome work. You don't like it for aesthetic reasons, pre-conceptions of aesthetic purity. That's fine too and I think I agree. But it's awesome work.

Go ahead. It is all yours, awesome work is simple work. Vercel wants React to do everything so they can sell everything. Not to me. That was a sad takeover of an open source project tho

Re: Migrating our backend from Vercel to Fly.io

#89
post #56

Earlier quoted context omitted.

> The people who use Vercel don't know anything about how to deploy on AWS Ehhhh. I’ve been deploying to AWS professionally for years and I’d choose Vercel for a personal project any day of the week. Life’s too short to play devops/sysadmin/sre without someone paying you the big bucks.

This. Anyone who has done enough ops knows that a platform (Vercel, Heroku, Netlify etc) which lets devs connect a git repo with a couple of clicks, and deploys automatically happen is a good devops experience. This is great for personal projects. This is great for budding projects in a professional setup as well.

If I never again have to write a httpd.conf or nginx.conf file from scratch it will be too soon.

Re: Migrating our backend from Vercel to Fly.io

#90
post #49

Earlier quoted context omitted.

> You always "need" to care about the abstraction that your infrastructure is providing to you. Sure. But as long as it implements something reasonable, you don't care about the details of how. "Runs version x of this programming language" is generally an easier abstraction to run business functionality on than "it's an x86-compatible computer". > Now add background tasks or streaming responses or a cron job. Oh, gue…

> Cron is a terrible model for actually solving business problems with. Do you know what happens when a cron job fails to run/errors out? Do lambdas not fail to run / error out? I’m not following.

> Do lambdas not fail to run / error out? I’m not following.

You generally have some kind of monitoring/alerting built in. With cron the usual behaviour is to email root@localhost using local sendmail, which generally achieves nothing except for filling up /var.

Post reply on HN