Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Migrating our backend from Vercel to Fly.io

openstatus.dev

Post reply on HN
Print view View original

121–130 of 160 posts

Re: Migrating our backend from Vercel to Fly.io

#121

Post by preciousoo »

intelVISA wrote: post #98
Lucasoato wrote: post #13

I really don’t understand how people can trust platforms like Vercel, Fly.io over robust could providers like Cloudflare, AWS or Azure. I mean, Vercel has its usefulness, it’s so well integrated with the NextJS stack, it totally makes sense for small amateurish projects since it saves you time and money… but once you want to push to production, have real customers and satisfy them reliably, these platforms can’t comp…

The only platform you can truly trust is the one you handcraft down to the NAND gates.

If you’re not mining your lithium and cobalt with your own handmade pickaxe you’re doing it wrong

Re: Migrating our backend from Vercel to Fly.io

#122

Post by preciousoo »

schneems wrote: post #55

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 discovered fly because I made an heroku account, connected the wrong card (I’m a broke college student), and heroku told me I couldn’t change the card for the next 30 days. This was all within 5 mins of making my account. I couldn’t find a support avenues.

I tried many clever workarounds but their alt-account defector is top notch (props to that team).

Asked around in dev circles and they recommended me fly io.

Idk who hurt heroku for them to put such measures in place but I’ve never encountered such strict policies before, and I’ll forever avoid places like that.

Re: Migrating our backend from Vercel to Fly.io

#123

Post by antod »

brundolf wrote: post #81
drwl wrote: post #58

Earlier quoted context omitted.

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)

That's a good way of describing it. Another issue is they've locked a whole lot of useful (practically required these days) features behind requiring an enterprise account - the trouble is that "enterprise" isn't just paying a whole lot more (if only). Enterprise involves getting involved in Salesforce style opaque fixed priced annual paid upfront contracts etc. It's just not a cloud provider any more at that point - you know the whole elastic thing the cloud was supposed to do.

Re: Migrating our backend from Vercel to Fly.io

#124

Post by OJFord »

Swizec wrote: post #103
OJFord wrote: post #94

Earlier quoted context omitted.

Either you mean 'too late ' or that's a complicated way of making a dissenting point?

It’s an idiom that means I never want to do this again. Even if I waited an infinite amount of time, it would still be too soon to have to write httpd.conf or nginx.conf files again. https://hinative.com/questions/337452

I'm a native English speaker, I'm well aware of the (misused here) idiom.

You could also have said 'ever' instead of 'never', that would be a simpler and better fix on re-reading.

Re: Migrating our backend from Vercel to Fly.io

#125

Post by kdazzle »

pech0rin wrote: post #20

I find it interesting that people seem to be trading short term gains with long term reliability and maintenance costs. This glut of 0-friction deploy services lull people into a nice false sense of security. But in actuality you are wasting hours, days, weeks of time when they become unreliable, support is unresponsive, or something unexpected pops up. There is a huge advantage (outside of amateur, low importance pr…

Azure actually had a nice Heroku-like service that served me well for a couple years. I forget what it’s called, but it’s probably the one reason I’d ever consider choosing Azure if that was ever my call to make.

Re: Migrating our backend from Vercel to Fly.io

#126

Post by tmikaeld »

hipadev23 wrote: post #109
ushakov wrote: post #66

Earlier quoted context omitted.

Their stack speaks for itself: Next.js, TailwindCSS, shadcn/ui, tinybird, turso, drizzle, clerk, Resend That’s for an app which sends a ping to a URL every x minutes…

> That’s for an app which sends a ping to a URL every x minutes… My bigger question is: How the fuck do these companies keep getting created? There's gotta be more uptime-monitor SaaS companies than todo MVC demos in existence.

It’s easy to get the free users, where of just a smaller % need to upgrade to keep you afloat. Then there’s the possibility to upsell other related services like analytics or logs.

Betterstack did this very well.

Re: Migrating our backend from Vercel to Fly.io

#127

Post by aurareturn »

meiraleal wrote: post #106
junon wrote: 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…

I started using Next.js in 2017. It made React a real production framework. Prior to Next.js, React was hard to setup and maintain and hard to make it go fast (on first load). Next.js solved the worst React problems.

I don't think it ruined React at all. I think it helped React gain in popularity - which you might interpret as "destruction".

Re: Migrating our backend from Vercel to Fly.io

#129

Post by globalise83 »

OJFord wrote: post #96
reducesuffering wrote: post #72

Earlier quoted context omitted.

Apologies. Yes, big tech == overrated, Vercel tech == underrated

It's 'beyond the level of inadequacy' which is amusingly ambiguous!

They reliably exceed 99.99% inadequacy overachievement - there, made it less ambiguous for you.

Re: Migrating our backend from Vercel to Fly.io

#130

Post by NicoJuicy »

radicalriddler wrote: post #113
benwaffle wrote: post #108

Earlier quoted context omitted.

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.

Correct. Which was actually already in my tldr

> TLDR: They could have done it cheaper, quicker and without adding DevOps to their workload with just migrating to Cloudflare.

See: quicker= less changes required to migrate...

Post reply on HN