| Why is anyone on HN "dunking" on Fly.IO of all companies? Michael - Don't take the bait. As someone who has zero affiliation with Fly.IO other than a few PR's to their OSS(I don't even know Michael), I greatly appreciate the contributions they have given back to the community. There are a lot of great hosting companies. Fly.IO stands out due to their revolutionary architecture and contributions back to the OSS community. I wish more companies operated like this. It's understandable some are upset about an outage. But Fly is doing really interesting and game-changing things, not copying a traditional vmware, cpanel or k8s route. Just as a reminder to what this company has offered back to everyone. SQLite: Ben Johnson's OSS work around SQLite stands out. Fly.IO and his work have really made sqlite a contender.
- https://fly.io/blog/all-in-on-sqlite-litestream/
- https://fly.io/blog/introducing-litefs/
- https://github.com/superfly/litefs
- https://github.com/benbjohnson/litestream
- https://fly.io/blog/sqlite-internals-wal/
- https://fly.io/blog/wal-mode-in-litefs/ Who really considered sqlite as a production option before Fly and Ben? Not me. Firecracker: Firecracker is amazing, but difficult to debug when something bad happens. There aren't a ton of people in devops who would share what they have. If you've ever used Firecracker, you've really been helped a lot by the various guides they have provided back to the community like these:
- https://fly.io/docs/reference/architecture/
- https://fly.io/blog/fly-machines/
- https://fly.io/blog/sandboxing-and-workload-isolation/ Their architecture is beautiful and revolutionary. They're probably the first or second ones to find a lot of the new edge cases as they grow. It's a lot harder to be the first one over the wall than it is to copy. They've literally given the average developer a blueprint to build scalable businesses that compete with their own. |