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.
Migrating our backend from Vercel to Fly.io
111–120 of 160 posts
Re: Migrating our backend from Vercel to Fly.io
#112From one toy to another.
Are Adobe, Splunk, Washington Post, Netflix, Zapier, Notion, and Uber toys? Because they're running on Vercel infra.
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
#113Earlier 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
Re: Migrating our backend from Vercel to Fly.io
#114Earlier 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…
Respectfully, you have no idea what you're talking about.
Re: Migrating our backend from Vercel to Fly.io
#115Re: Migrating our backend from Vercel to Fly.io
#116I’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).
Re: Migrating our backend from Vercel to Fly.io
#117I feel like this should be a high priority. Deployments should be quickly reversible so that a livesite caused by a bad deployment can be mitigated quickly.
Re: Migrating our backend from Vercel to Fly.io
#118Earlier 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.
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
#119TLDR: 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…
Re: Migrating our backend from Vercel to Fly.io
#120Earlier 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…
Vercel is doing nothing but trying to improve DX for all the things people complain about React.