4 ms·

I'm a big DO fan as their pricing models are easier to understand, and use them myself for personal projects, but I would hesitate to use some of their products

by lukevp 6y ago

I'm a big DO fan as their pricing models are easier to understand, and use them myself for personal projects, but I would hesitate to use some of their products at an enterprise. The reason is that they do not seem committed to SLAs and offering metrics around their reliability. One example of this is in DO Spaces [1]. Nowhere on their site do they say the durability of the data, or whether they have multiple AZs within one DC for availability, or anything like that. Compare that with AWS S3, where the 11 9's of durability is front and center on the page [2]. Marketing Spaces as S3-compatible without providing transparency on the reliability of the underlying storage engine feels disingenuous to me. Especially when, upon investigation, there are several complaints of data loss on the Spaces storage engine with DO not able to provide assistance [3]. Now whether that's an issue for a container registry, maybe not so much, since you can likely rebuild containers if you have reproducible builds, but it's a pattern I've seen across their offerings. [1]: https://www.digitalocean.com/products/spaces/ https://www.digitalocean.com/products/spaces/ [2]: https://aws.amazon.com/s3/ https://aws.amazon.com/s3/ [3]: https://news.ycombinator.com/item?id=17225665 https://news.ycombinator.com/item?id=17225665

tebbers 6y ago
I also noticed this with their managed databases product and was the main reason why I went with AWS RDS - they don't have availability zones so if they have a data centre issue, all your database instances including your standby nodes could be affected.
csunbird 6y ago
Spaces are build on ceph, as far as I can understand. Edit: It is mentioned here https://www.digitalocean.com/docs/spaces/ https://www.digitalocean.com/docs/spaces/
BillinghamJ 6y ago
That S3 number is not an SLA. It's just saying that's what they're hoping they'll achieve by its design.
throwaway201103 6y ago
As we've seen recently, with cloud providers you are at the mercy of their "sole discretion" judgment on terms of service violations. You could be shut down tomorrow with no recourse. So you still have to do all your own backups and continuity of operations planning across different providers or in-house. To me this really calls into question the entire value proposition, since if you want to be safe you need to have the ability to redeploy your entire business on another provider at a moment's notice.

by lukevp 6y ago

tebbers 6y ago

I also noticed this with their managed databases product and was the main reason why I went with AWS RDS - they don't have availability zones so if they have a data centre issue, all your database instances including your standby nodes could be affected.

csunbird 6y ago

Spaces are build on ceph, as far as I can understand. Edit: It is mentioned here https://www.digitalocean.com/docs/spaces/ https://www.digitalocean.com/docs/spaces/

BillinghamJ 6y ago

That S3 number is not an SLA. It's just saying that's what they're hoping they'll achieve by its design.

throwaway201103 6y ago

As we've seen recently, with cloud providers you are at the mercy of their "sole discretion" judgment on terms of service violations. You could be shut down tomorrow with no recourse. So you still have to do all your own backups and continuity of operations planning across different providers or in-house. To me this really calls into question the entire value proposition, since if you want to be safe you need to have the ability to redeploy your entire business on another provider at a moment's notice.