Live data from Hacker News

Migrating our backend from Vercel to Fly.io

openstatus.dev

111–120 of 160 posts

Re: Migrating our backend from Vercel to Fly.io

#111
I joined a project that was fully deployed on Vercel. We routinely ran into issues with limitations, outages and sharp edges. Our junior devs had also taken advantage of Vercel specific features (I remember a Vercel specific request object in the code specifically).

Given all the problems and the vendor lock in from tight coupling I advise everyone I discuss Vercel with to avoid them like the plague.

Re: Migrating our backend from Vercel to Fly.io

#112
post #44

From one toy to another.

Are Adobe, Splunk, Washington Post, Netflix, Zapier, Notion, and Uber toys? Because they're running on Vercel infra.

Its not about vercel or fly.io. Its about openstatus dev

Their migration timeline from their blog:

1. August 2, 48 hours after public launch 400+ users

2. August 20, migrate from planetscale to turso (sqlite)

3. Oct 29, migrate from vercel to fly.io, migrate from nextjs to hono, also mentioned change to bunjs.

This is seems like they tend to (sorry I'm judging here):

1. move fast break things or

2. don't have a plan before launch day or

3. only chasing the latest tech buzz.

Re: Migrating our backend from Vercel to Fly.io

#113

Earlier quoted context omitted.

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

Fly.io supports up to 8GB docker images

Cool. By the sounds of it, they needed the docker image in the first place because they chose fly.io. This guy is saying that Cloudflare wouldn't support it, but if they went the cloudflare route (which I'm not saying whether or not it's actually possible), they wouldn't have needed the docker image in the first place.

Re: Migrating our backend from Vercel to Fly.io

#114
post #105

Earlier quoted context omitted.

They are objectively not that, lol. If you don't like what they're doing I understand but please don't disrespect people you don't know.

That's what you get for working in a famous company that took over an open source software. If the destruction of React by Vercel paid your bills and you feel disrespected by my total despise for this get rich fast schema (a la crypto rugpulls), that's a problem for you to solve, not me. Edit: but in reality I'm happy and thankful to Vercel for imploding React, it helped me to finally check that there are so many bet…

How did Vercel "destroy" React? How are they a "get rich quick" "rugpull"?

Respectfully, you have no idea what you're talking about.

Re: Migrating our backend from Vercel to Fly.io

#116
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).

We’ve run Domainr on Heroku for over a decade, and it’s been rock solid all along.

Re: Migrating our backend from Vercel to Fly.io

#118
post #95
post #93

Earlier quoted context omitted.

Some people avoid large providers, since large providers have approximately no incentive whatsoever to keep you, specifically , as a customer. I.e. large providers will happily raise their prices, alter the deal, throw you under the bus, disable your account, delete all you data and then refuse to talk to you. They can do this because, when they look at the big picture, you don’t matter to them. And since doing this…

And a small service can go under anytime, without any real warning. Most big providers end up being cheaper for you as well. Vercel is insanely expensive.

> And a small service can go under anytime, without any real warning.

Both large and small providers could make the ground from under your feet disappear, in different ways. But only the small provider has a real incentive to actually keep you, as just one customer. It’s only when a small provider goes out of business completely that you have any risk. And that’s unlikely to happen, unless they’re delusional or funded by squirrel-minded VCs – which are things you can determine beforehand.

Re: Migrating our backend from Vercel to Fly.io

#119

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…

It is beyond me why anyone but the most pre-revenue bootstrapped projects would spend $150k+/yr eng hours into saving $100 month on infra. Projects like this are trying to make $1m+/yr in revenue.

Re: Migrating our backend from Vercel to Fly.io

#120
post #105

Earlier quoted context omitted.

They are objectively not that, lol. If you don't like what they're doing I understand but please don't disrespect people you don't know.

That's what you get for working in a famous company that took over an open source software. If the destruction of React by Vercel paid your bills and you feel disrespected by my total despise for this get rich fast schema (a la crypto rugpulls), that's a problem for you to solve, not me. Edit: but in reality I'm happy and thankful to Vercel for imploding React, it helped me to finally check that there are so many bet…

Dan Abramov, de facto lead for React, said that the React team was driving the vision behind the new features in React. Vercel just said, "how can we help? You guys think server components are great, ok, we'll make them first class as that's where the React ecosystem is headed."

Vercel is doing nothing but trying to improve DX for all the things people complain about React.

Post reply on HN