Live data from Hacker News

Migrating our backend from Vercel to Fly.io

openstatus.dev

131–140 of 160 posts

Re: Migrating our backend from Vercel to Fly.io

#131

Earlier quoted context omitted.

Edge functions are cost effective, the problem is that they are comparing from Vercel. Vercel is basically a dev friendly wrapper for tier 1 services: https://news.ycombinator.com/item?id=35774730 Eg. Vercel is 25x more expensive than eg. Cloudflare Workers. Raw guess would be that their 150$ bill would have become 6$. https://news.ycombinator.com/item?id=37891412 Eg. Image resizing > Vercel : 5$ / 1000 requests > Cl…

According to this page at Cloudflare, their pricing is 50 cents per 1000, is that correct? Or is it a different product... https://blog.cloudflare.com/merging-images-and-image-resizin...

50,000 monthly resizing requests included with Pro, Business. $9 per additional 50,000 resizing requests

https://www.cloudflare.com/plans/ - section: image resizing

Re: Migrating our backend from Vercel to Fly.io

#132

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.

This was done in a weekend fyi ( mentioned in the blog post)

Re: Migrating our backend from Vercel to Fly.io

#133

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…

Several SaaS companies are pushing for Next.js as their main SDK, that is how real customers end up in Vercel.

Re: Migrating our backend from Vercel to Fly.io

#134

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…

Founder of OpenStatus here: We can't use Cloudflare because there's no way to execute in a specific region, if you know how to do it let me know

Re: Migrating our backend from Vercel to Fly.io

#135
post #112

Earlier quoted context omitted.

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…

We are trying, breaking and learning.

And you were right we did not have plan before launch, we wanted to build something that bring us excitement. and we are planing more about the future, since the project took off

FYI we still both have full time job

Re: Migrating our backend from Vercel to Fly.io

#137
post #23

Earlier quoted context omitted.

> 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…

Also, if you implement it as lambdas, your solution is now less portable. Your EC2 instance can probably be ported to something else easier than some lambda solution.

That's for abstractions to take care of. If my CI platform offers a lambda runner instead of an ec2 integration, I would use it in a heartbeat.

Also, it's a 5 line shell script that already depends on 2 AWS services (SSM and IAM) that makes an API call to a third AWS service (S3). It's already locked to AWS

Re: Migrating our backend from Vercel to Fly.io

#138
post #23

Earlier quoted context omitted.

> 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.

I wrote it. It was a 50 line packerfile with a shell script that installs buildkite, docker, and the AWS cli, and hasn't been touched in 2 years other than bumping version numbers.

Re: Migrating our backend from Vercel to Fly.io

#139

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?

(Fly customer for the past 12 months: small web app (three machines across two regions plus replicated Postgres across two regions, on a paid plan)). Fly has been extremely stable for us, with the sole exception of deploys: once a month or so, deploys from CI start failing for a couple of hours. That doesn’t result in any downtime (I have never experienced any downtime due to a failing machine on Fly), just that new…

Thanks for the insight!

Re: Migrating our backend from Vercel to Fly.io

#140

Earlier quoted context omitted.

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

If you don't have your own star spitting out bespoke elements, are you really doing it at all, or just using someone else's work
Post reply on HN