3 ms·

Personally I am partial to heterogeneous deployments across commodity vendors like Digital Ocean, Vultr, Linode, OVH, etc. You do have to think a little bit mor

by api 10y ago

Personally I am partial to heterogeneous deployments across commodity vendors like Digital Ocean, Vultr, Linode, OVH, etc. You do have to think a little bit more about security and devops but you get a lot of power and robustness for a lot less money. We do use S3 for backups and big storage. That has no equal.

danieltillett 10y ago
This is exactly what I do and I have had 100% uptime for the last two years.
- api 10y ago
  But that's not Enterprise(tm)! Seriously... I feel like the Big Cloud vendors are making a ton of money convincing a lot of people that you're not doing it right if you're not using their stuff.
devonkim 10y ago
Every time I do the math the bandwidth egress costs of AWS and GCE become rather large and non-trivial. How do you make it work for your workloads?
- api 10y ago
  We don't use AWS or GCE. The other providers don't charge anywhere close to as much for bandwidth... to the point that deploying across multiple providers and using the Internet as our backplane network is no issue. One trick I like is to split infrastructure across 2-3 different providers at at least three different nearby data centers. Example: Chicago (Vultr), Toronto (DO), Montreal (OVH). Latency is low enough for most replication purposes and if one experiences a massive failure the other two will be fine. 3/3 failure probably requires alien invasion or global thermonuclear war.
boulos 10y ago
Google Cloud Storage (GCS) is in my (biased) opinion better than S3 in most ways. GCS's default buckets just work within all the US. For no extra $$, you get something you can read and write to at massive throughput in us-west1 (Oregon), us-central1 (Iowa) and us-east1 (South Carolina). This has totally changed how people use our compute offering compared to say EC2 plus S3. Similarly, we introduced Nearline which S3 sort of copied with Infrequent Access. Except S3-IA rounds all files up to 128 KB. Nearline is simple $.01/GB/month plus $.01/GB retrieved. All of this with the team maintaining their own JSON API and compatibility with the S3 API (which I use from my NAS box at home). tl;dr: GCS easily goes head to head with S3 (and often comes out on top). Disclosure: I work on Google Cloud (and use GCS myself).

by api 10y ago

danieltillett 10y ago

This is exactly what I do and I have had 100% uptime for the last two years.

api 10y ago
But that's not Enterprise(tm)! Seriously... I feel like the Big Cloud vendors are making a ton of money convincing a lot of people that you're not doing it right if you're not using their stuff.

devonkim 10y ago

Every time I do the math the bandwidth egress costs of AWS and GCE become rather large and non-trivial. How do you make it work for your workloads?

api 10y ago
We don't use AWS or GCE. The other providers don't charge anywhere close to as much for bandwidth... to the point that deploying across multiple providers and using the Internet as our backplane network is no issue. One trick I like is to split infrastructure across 2-3 different providers at at least three different nearby data centers. Example: Chicago (Vultr), Toronto (DO), Montreal (OVH). Latency is low enough for most replication purposes and if one experiences a massive failure the other two will be fine. 3/3 failure probably requires alien invasion or global thermonuclear war.

boulos 10y ago

Google Cloud Storage (GCS) is in my (biased) opinion better than S3 in most ways. GCS's default buckets just work within all the US. For no extra $$, you get something you can read and write to at massive throughput in us-west1 (Oregon), us-central1 (Iowa) and us-east1 (South Carolina). This has totally changed how people use our compute offering compared to say EC2 plus S3. Similarly, we introduced Nearline which S3 sort of copied with Infrequent Access. Except S3-IA rounds all files up to 128 KB. Nearline is simple $.01/GB/month plus $.01/GB retrieved. All of this with the team maintaining their own JSON API and compatibility with the S3 API (which I use from my NAS box at home). tl;dr: GCS easily goes head to head with S3 (and often comes out on top). Disclosure: I work on Google Cloud (and use GCS myself).