News for hackers. Stuff that matters.
Re:Rapid growth, lessons learned and improvements at Fly.io by latchkey on Monday March 06, 2023 @02:56PM (#35046719)
> What I truly want and probably lots of other people too is Flyctl for AWS. The same simplicity to run as fly, but give me something cheap in Virginia or the Dalles.

Google Cloud. It is painfully easy to spin up managed postgres, super easy to deploy gcp cloud functions or gcp cloud run. It isn't expensive either and just works.

Re:Rapid growth, lessons learned and improvements at Fly.io by 0cf8612b2e1e on Monday March 06, 2023 @03:00PM (#35046766)
If someone is not already using the holy trinity (AWS/Azure/GCP) there is probably a reason.
Re:Rapid growth, lessons learned and improvements at Fly.io by monsieurbanana on Monday March 06, 2023 @03:16PM (#35046965)
I'm not using gcp anymore because it's not worth risk losing access to my personal gmail account just to play around with pet projects.

I might be paranoid, but I just don't feel comfortable when there's so much in play.

Re:Rapid growth, lessons learned and improvements at Fly.io by guhcampos on Monday March 06, 2023 @03:33PM (#35047181)
Create a new Gmail account?
Re:Rapid growth, lessons learned and improvements at Fly.io by vineyardmike on Monday March 06, 2023 @04:35PM (#35047979)
Google associates different accounts that are from the same owner when handling issues FYI. So if they think your account is doing something wrong on GCP, be wary of associated accounts.
Re:Rapid growth, lessons learned and improvements at Fly.io by latchkey on Monday March 06, 2023 @10:51PM (#35051330)
Never once heard of that.
Re:Rapid growth, lessons learned and improvements at Fly.io by miyuru on Tuesday March 07, 2023 @12:54AM (#35052064)
Re:Rapid growth, lessons learned and improvements at Fly.io by latchkey on Tuesday March 07, 2023 @12:13PM (#35057956)
Did you read the comments? My takeaway is that it was bs.
Re:Rapid growth, lessons learned and improvements at Fly.io by 0cf8612b2e1e on Tuesday March 07, 2023 @02:44PM (#35060172)
There was one person strongly challenging the story and plenty of back and forth. It hardly seems a settled case one way or the other.
Re:Rapid growth, lessons learned and improvements at Fly.io by namaria on Monday March 06, 2023 @04:40PM (#35048039)
Separating concerns, isolating things that are not related, these are some basic tenets of good engineering. Yet we all keep rolling the ball of mud downhill and act shocked it keeps growing and swallowing everything.
Re:Rapid growth, lessons learned and improvements at Fly.io by latchkey on Tuesday March 07, 2023 @12:14PM (#35057985)
That's the beauty of the services I named. Super easy to roll the code to any other similar PaaS provider. There is no vendor lockin.

It is postgres + http handlers.

Re:Rapid growth, lessons learned and improvements at Fly.io by 0cf8612b2e1e on Monday March 06, 2023 @04:36PM (#35047987)
Totally agree with this mindset. My digital life is on the line because Google refuses to separate services.
Re:Rapid growth, lessons learned and improvements at Fly.io by amluto on Monday March 06, 2023 @05:04PM (#35048365)
Egress pricing, for one.

fly.io charges an outrageous 2 cents/GB. Google is over 4x that.

At fly.io rates, 1Gbps average over a month is $6400/mo. Google is tiered and you’re looking at over $10k/mo.

For comparison, a cheap managed switch that can handle 1Gbps cost about $100, maybe a bit more if you want a nice one. A nice router is more. You can rent an entire rack, including power, cooling, and an unmetered 1Gbps for $300-$1k/mo (with maybe some wiggle room on both ends). You can buy a pretty nice server, amortize the price over a week or two, and still come out ahead.

You certainly get considerable value from a major cloud provider, and a lot of their other services are reasonably priced, but, depending on your workload, the egress prices and the corresponding Hotel California factor may make using a major cloud provider a poor proposition.

Re:Rapid growth, lessons learned and improvements at Fly.io by re-thc on Tuesday March 07, 2023 @07:33AM (#35054598)
It's potentially a lot more for the big clouds. Anything in the network path has a charge - load balancers, NAT gateways, etc.
Re:Rapid growth, lessons learned and improvements at Fly.io by amluto on Tuesday March 07, 2023 @09:50AM (#35055941)
The cost of egress plus a gateway or two is fairly close to the cost of burning a DVD twenty years ago. And it appears to actually be cheaper to burn DVDs and mail them today than to send data from a major cloud.

This becomes very relevant for things like archiving data. If you generate data outside of a major cloud, you can pay a major cloud a very reasonable fee to archive it for you. But if you ever download your archive, it will cost you about half the price of buying an external disk to store it on.

(To be fair, object storage is rather more reliable than a single crappy external drive. But if you access the data more than once, maybe you should have a colo or on-prem copy too.)

Re:Rapid growth, lessons learned and improvements at Fly.io by latchkey on Tuesday March 07, 2023 @12:16PM (#35058011)
Depending on what I'm building, I tend to cache on the edge with something like CloudFlare in front of GCP. Lowers the egress charges significantly, with the benefit of speeding everything up too.
Re:Rapid growth, lessons learned and improvements at Fly.io by mattbillenstein on Monday March 06, 2023 @03:02PM (#35046789)
Do you have a guide in mind?

If it's sorting and sifting and clicking a bunch of stuff in the console, that's not painfully simple. If it's some easy cli commands, I think that's in the ballpark...

Re:Rapid growth, lessons learned and improvements at Fly.io by latchkey on Monday March 06, 2023 @10:52PM (#35051333)
There is a gcloud cli, but I just automated deployments in CI...

https://github.com/google-github-actions/deploy-cloud-functi...