News for hackers. Stuff that matters.
Re:Issues with upstream DNS provider by mtlynch on Tuesday August 23, 2022 @07:58PM (#32573261)
Left Heroku for Fly.io a year or so ago and have been very happy.
Re:Issues with upstream DNS provider by nicoburns on Tuesday August 23, 2022 @08:51PM (#32573658)
How have you found uptime on fly.io (and are you using multiple instances for a high-availability setup?). We've been running on Heroku without HA, and it's been good enough, and wondering if we might expect to be able to get away with that on fly.io too...
Re:Issues with upstream DNS provider by mtlynch on Tuesday August 23, 2022 @10:16PM (#32574237)
Uptime has mostly been good, although I didn't set up alerting for any of my Fly projects until recently. All my apps are running on a single node per app, so I haven't tried

The one notable outage was this bug where Fly was evicting smaller instances at overloaded DCs rather than preventing new apps from acquiring resources:

https://community.fly.io/t/app-stuck-in-pending-state-after-...

The workaround was to upgrade to a larger instance, but I probably evicted someone else.

Re:Issues with upstream DNS provider by ab-dm on Tuesday August 23, 2022 @08:30PM (#32573512)
Did you use the https://fly.io/launch/heroku migration page? It almost looks too good to be true.
Re:Issues with upstream DNS provider by mtlynch on Tuesday August 23, 2022 @10:10PM (#32574216)
No, I wasn't using much Heroku-specific. All of my apps run in Docker containers, so it's mostly just migrating my CI to deploy to Fly instead of Heroku.

I did get a lot of perf increases moving from GCP to Fly, but I think I have to credit most of the improvements to SQLite being faster than Firestore:

https://mtlynch.io/retrospectives/2021/12/#migrating-my-side...

Re:Issues with upstream DNS provider by Exuma on Tuesday August 23, 2022 @08:58PM (#32573730)
wow it def does lol