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

101–110 of 160 posts

Re: Migrating our backend from Vercel to Fly.io

#101

Post by intelVISA »

maccard wrote: post #23
rjh29 wrote: 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.

> People using lambda functions are getting ripped off, they could just buy a couple of VPS. A non-zero amount of our CICD pipelines are "perform API call with secret pulled from SSM/Secrets Manager". They happen 1-2 times per day and take less than a 5 seconds to run on each invocation. We currently have a burstable EC2 instance running 24/7 to handle these which costs us ~$5/mo. My napkin math says that this would…

I'm guessing the original developer was only $50/hr with a cheap, non-scaling setup like that.

Re: Migrating our backend from Vercel to Fly.io

#102

Post by elforce002 »

Swizec wrote: post #56
dboreham wrote: post #40

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 x100. I use gcp, DO, and Vultr, for almost everything (ml, be, vas, etc.) but for webapps, vercel wins 9/10 times.

Re: Migrating our backend from Vercel to Fly.io

#103

Post by Swizec »

OJFord wrote: post #94
Swizec wrote: post #89

Earlier quoted context omitted.

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

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

Re: Migrating our backend from Vercel to Fly.io

#104

Post by Rapzid »

yowlingcat wrote: post #64
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…

> 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. I find it interesting as well. I agree that it's a false sense of security, and there is no real long-term gain from avoiding the one time paydown of deploying to a big 3 cloud services provider. Still, I thin…

The latest effort from AWS to address this seems to be copilot.

Re: Migrating our backend from Vercel to Fly.io

#105

Post by junon »

meiraleal wrote: post #83
reducesuffering wrote: post #53

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

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.

Re: Migrating our backend from Vercel to Fly.io

#106

Post by meiraleal »

junon wrote: post #105
meiraleal wrote: post #83

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

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 better options nowadays.

Re: Migrating our backend from Vercel to Fly.io

#107

Post by itake »

elxx wrote: post #70
robertlagrant wrote: post #38

Why is Fly apparently so unstable? I like many love the idea, but get a little scared by the many many anecdotes of issues. What are they doing that makes it unstable? Lots of new locations spinning up that shake bugs loose? Cost-reducing refactorings that reduce stability?

(Background: I'm currently using Fly for some hobby apps. I like it.) It is still wildly unstable right now because they're basically still building the platform and figuring out how to run a business. Earlier this year there was a migration to their "Apps V2" platform [0] which was supposed to be simple but it was extremely poorly communicated which led to a lot of users hitting issues along the way and being forced…

I lost data in the v2 migration with down time. their support (engineers?) are customer facing and unprofessional.

Re: Migrating our backend from Vercel to Fly.io

#108

Post by benwaffle »

radicalriddler wrote: post #82
grrowl wrote: post #43

Earlier quoted context omitted.

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?

Fly.io supports up to 8GB docker images

Re: Migrating our backend from Vercel to Fly.io

#109

Post by hipadev23 »

ushakov wrote: post #66
oefrha wrote: post #61

Earlier quoted context omitted.

This is what happens when you do HN-frontpage-driven development. I mean, they use Bun (which I’m sure will be great in a couple years’ time) and quickly ran into an fd leak in it. Does that sound like a production grade runtime? However, I suppose it’s good for content marketing. You’re not going to make front page by choosing boring old technology (unless you’re migrating back to boring old technology after failed…

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.

Re: Migrating our backend from Vercel to Fly.io

#110

Post by hipadev23 »

elxx wrote: post #70
robertlagrant wrote: post #38

Why is Fly apparently so unstable? I like many love the idea, but get a little scared by the many many anecdotes of issues. What are they doing that makes it unstable? Lots of new locations spinning up that shake bugs loose? Cost-reducing refactorings that reduce stability?

(Background: I'm currently using Fly for some hobby apps. I like it.) It is still wildly unstable right now because they're basically still building the platform and figuring out how to run a business. Earlier this year there was a migration to their "Apps V2" platform [0] which was supposed to be simple but it was extremely poorly communicated which led to a lot of users hitting issues along the way and being forced…

I still don't know what Fly Apps vs Fly Machines are and I stopped caring about their service as a result.
Post reply on HN