News for hackers. Stuff that matters.
Re:How We Knew It Was Time to Leave the Cloud by sytse on Sunday November 13, 2016 @04:06AM (#12942509)
Yep, and we at GitLab have Direct Connect to AWS as a requirement for picking out new colo.
Re:How We Knew It Was Time to Leave the Cloud by Pyxl101 on Sunday November 13, 2016 @06:07AM (#12942808)
If you guys use AWS, have you taken a look at EBS provisioned IOPS? EBS provisioned IOPS comes to mind here since it allows you to specify the desired IOPS of a volume, and provides an SLA.

> Providers don't provide a minimum IOPS, so they can just drop you.

The reason I ask is because the blog post generalizes a lot about what cloud providers offer or what the cloud is capable of, but doesn't explore some of the options available to address those concerns, like provisioned IOPS with EBS, dedicated instances with EC2, provisioned throughput with DynamoDB, and so on.

Re:How We Knew It Was Time to Leave the Cloud by sytse on Sunday November 13, 2016 @08:01AM (#12943126)
EBS goes up to 16TB, we need an order of magnitude more.

You're right that the blog post was generalizing.

BTW We looked into AWS but didn't want to use an AWS only solution because of maximum size, costs, and the reusability of the solution.

Re:How We Knew It Was Time to Leave the Cloud by hagbarddenstore on Monday November 14, 2016 @04:36AM (#12948610)
Per disk. You can attach multiple disks to a single EC2 node.

So, RAID multiple EBS volumes and you have a larger disk.