Live data from Hacker News

Migrating our backend from Vercel to Fly.io

openstatus.dev

91–100 of 160 posts

Re: Migrating our backend from Vercel to Fly.io

#91

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

That's awesome work. You don't like it for aesthetic reasons, pre-conceptions of aesthetic purity. That's fine too and I think I agree. But it's awesome work.

[deleted]

Re: Migrating our backend from Vercel to Fly.io

#92

Earlier quoted context omitted.

That's awesome work. You don't like it for aesthetic reasons, pre-conceptions of aesthetic purity. That's fine too and I think I agree. But it's awesome work.

Go ahead. It is all yours, awesome work is simple work. Vercel wants React to do everything so they can sell everything. Not to me. That was a sad takeover of an open source project tho

I like to joke that because Vercel doesn't make money when you run components in the client, and React is now made for Vercel, that React is now developed for backends.

I'm a big fan of OSS projects being sponsored by companies that use them for a higher level business. Vs a ton of the C# ecosystem where they try to sell you the library/framework.

But hosting businesses ain't it when it comes to frameworks.. It creates weird incentives.

Re: Migrating our backend from Vercel to Fly.io

#93

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…

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 saves them some money, they all do it.

Re: Migrating our backend from Vercel to Fly.io

#94
post #89

Earlier quoted context omitted.

This. Anyone who has done enough ops knows that a platform (Vercel, Heroku, Netlify etc) which lets devs connect a git repo with a couple of clicks, and deploys automatically happen is a good devops experience. This is great for personal projects. This is great for budding projects in a professional setup as well.

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?

Re: Migrating our backend from Vercel to Fly.io

#95
post #93

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…

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.

Re: Migrating our backend from Vercel to Fly.io

#96

Earlier quoted context omitted.

I think this comment is intended as a compliment to Vercel, but it's hard to tell from the wording.

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

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

Re: Migrating our backend from Vercel to Fly.io

#97
post #49

Earlier quoted context omitted.

> You always "need" to care about the abstraction that your infrastructure is providing to you. Sure. But as long as it implements something reasonable, you don't care about the details of how. "Runs version x of this programming language" is generally an easier abstraction to run business functionality on than "it's an x86-compatible computer". > Now add background tasks or streaming responses or a cron job. Oh, gue…

The big advantage of Docker based solutions is that they're portable between providers. And you can ramp up the complexity as you need. Just need a language runtime? Then you can have a single-line Dockerfile. Need to support a native dependency? Then you might need to install it, but at least it will be possible to do that.

I can do all that with puppet without the extra complexity of containers.

Re: Migrating our backend from Vercel to Fly.io

#98

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.

Re: Migrating our backend from Vercel to Fly.io

#99
post #59

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…

Whats the use case for edge computing like Fly.io. I have yet to figure it out the use case where a edge provider is necessary. That is, having a database on the edge.

Lots of us (well, me at least) use fly because it's a bundled set of aws best practices that I could configure in aws if I wanted to, but I'd waste another week of my life. alb + various vpcs + autoscaling group + fargate + ecs + their super shitty vpn service to vpn to a console + rds + elasticache or... just type "fly deploy" and go from zero to live in 20 minutes.

That said, fly's deploys are flaky. I hope they get it fixed because the rest of the service is pretty good.

Re: Migrating our backend from Vercel to Fly.io

#100
post #71
post #62

Earlier quoted context omitted.

Having customers in places around the world. If you site is hosted in North Virginia, and you have customers in Australia, they are going to really suffer from the speed of light.

That’s very rare though. Unless you’re Shopify, location doesn’t really matter

Common enough to have a couple customers in the EU or apac who consistently complain that your site is glacial and it turns out to be pretty bad for them...
Post reply on HN