4 ms·

> The bad news is that I'd be out of a job if I chose your service in this instance. 47 hours is two full days. There was one physical server down. That's it.

> The bad news is that I'd be out of a job if I chose your service in this instance. 47 hours is two full days. There was one physical server down. That's it. They even brought it back. I've had AWS delete more instances, including all local NVMe store data, than I can count on my hands. Just in the last year. Those instances didn't experience 47 hours downtime, they experienced infinite downtime, gone forever. I guess by your standard I'd be fired for using AWS too. But no, in reality, AWS deletes or migrates your instances all the time due to host hardware failure, and it's fine because if you know what you're doing, you have multiple instances across multiple AZs. The same is true of fly. Sometimes underlying hardware fails (exactly like on AWS), and when that happens, you have to either have other copies of your app, or accept downtime. I'll also add that the downtime is only 47 hours for you if you don't have the ability to spin up a new copy on a separate fly host or AZ in the meanwhile.

the_duke 3y ago
The core issue here is that fly doesn't offer distributed storage, only local disks. Combine that with them having tooling for setting up Postgres built on top of single node storage, and you have the downtime problems and unhappy customers as a given.
yjftsjthsd-h 3y ago
When does AWS delete instances? Migrate, sure, and yes, local storage is supposed to be treated as disposable for that reason, but AFAIK only spot instances should be able to be destroyed outright.
- TheDong 3y ago
  To quote from their docs: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-retirement.html https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance... > If your instance root device is an instance store volume, the instance is terminated, and cannot be used again. See also the aws "Dedicated Hosts" and "Mac Instances". Those also have similar termination behavior. The majority of my instances lost are from the instance store thing.
- yencabulator 3y ago
  The underlying problem is that Fly doesn't provide non-local, less-eager-to-disappear, volumes.
Jupe 3y ago
Since the post said "cluster", I assumed it was a set of instances with replicas and the like. I've never experienced AWS killing nodes forever; at least not DB instances.

the_duke 3y ago

The core issue here is that fly doesn't offer distributed storage, only local disks. Combine that with them having tooling for setting up Postgres built on top of single node storage, and you have the downtime problems and unhappy customers as a given.

yjftsjthsd-h 3y ago

When does AWS delete instances? Migrate, sure, and yes, local storage is supposed to be treated as disposable for that reason, but AFAIK only spot instances should be able to be destroyed outright.

TheDong 3y ago
To quote from their docs: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-retirement.html https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance... > If your instance root device is an instance store volume, the instance is terminated, and cannot be used again. See also the aws "Dedicated Hosts" and "Mac Instances". Those also have similar termination behavior. The majority of my instances lost are from the instance store thing.
yencabulator 3y ago
The underlying problem is that Fly doesn't provide non-local, less-eager-to-disappear, volumes.

Jupe 3y ago

Since the post said "cluster", I assumed it was a set of instances with replicas and the like. I've never experienced AWS killing nodes forever; at least not DB instances.