Live data from Hacker News

Highly Available Block Storage

digitalocean.com

141–145 of 145 posts

Re: Highly Available Block Storage

#141

Earlier quoted context omitted.

Actually because I use the DO API and lots of small instances that work together, not that long. Right now I use S3, which blows because I hate the S3 cli and API, so I would love a better solution.

Not sure if it's much better for you use case, but Backblaze introduced an S3 competitor called B2 a few months ago. Price calculation is straightforward: - $0.005/GB/month for storage - $0.05/GB download - $0.004 per 10k downloads There is a base free tier as well. https://www.backblaze.com/b2/

Wow thanks for this! I'll definitely use these guys in the future.

Re: Highly Available Block Storage

#142
post #73

Earlier quoted context omitted.

Expecting a hosting provider to wade into fair use waters hand-in-hand with you is generally unwise. The vast majority will not unless you are a large customer with your own legal staff on retainer to provide the appropriate legalese/notices/etc.

I don't expect that, but I do expect that a company not immediately kowtow to an infringement request if there is some ambiguity as to whether it's infringing. That said, the original reporting on this and the statement from DigitalOcean are at odds (Motherboard's update with DO's statement), and since I haven't verified either, I'll retract any specific support for either side of this particular instance.

> I don't expect that, but I do expect that a company not immediately kowtow to an infringement request if there is some ambiguity as to whether it's infringing.

That requires money for a lawyer to evaluate it. If the customer has their own legal staff that does this and relays that opinion to the host, as well as being large enough to cover any legal costs DO might incur, DO would be fine with it.

You are basically saying you are entitled to using DO's legal staff and financial resources in addition to the hosting you've paid for.

Re: Highly Available Block Storage

#143

Earlier quoted context omitted.

The purpose of the block storage in this instance isn't about giving your vm/droplet more space. It's separation. That way any data that's on that device can be attached to another vm/droplet. It probably would be more cost effective just to upgrade the vm/droplet if space were a concern. It's at least how we've marketed the same feature for the past year or two via Codero's portal. Not to say I don't like how DO has…

Exactly! It's about having an easy upgrade path, generally reducing the amount of work for common operations, and for more flexibility engineering your cloud architecture. It's nice that it happens to be SSD, but highest performance or lowest cost per GB isn't necessarily the only cost saving factor. This a main reason I still use Amazon AWS: I can create an instance and if it doesn't perform, upgrade it until it doe…

What you describe was already possible on DO using snapshots (that can be stored for free), and that's what I usually do too.

Re: Highly Available Block Storage

#144
post #73

Earlier quoted context omitted.

I don't expect that, but I do expect that a company not immediately kowtow to an infringement request if there is some ambiguity as to whether it's infringing. That said, the original reporting on this and the statement from DigitalOcean are at odds (Motherboard's update with DO's statement), and since I haven't verified either, I'll retract any specific support for either side of this particular instance.

> I don't expect that, but I do expect that a company not immediately kowtow to an infringement request if there is some ambiguity as to whether it's infringing. That requires money for a lawyer to evaluate it. If the customer has their own legal staff that does this and relays that opinion to the host, as well as being large enough to cover any legal costs DO might incur, DO would be fine with it. You are basically…

> You are basically saying you are entitled to using DO's legal staff and financial resources in addition to the hosting you've paid for.

No, what I'm saying is that DO must already do this to some degree if they are handling requests, as otherwise I could send letters claiming trademark/copyright infringement for any number of things and get many customers shut down. If they have internal guidelines for what they do in cases when trademark/copyright infringement, I expect they follow those. I also expect that those policies do the minimum legally required of them. That's not because it's cheaper and garners good will from customers (it does), but because to do otherwise is taking sides in a legal situation without being an appointed arbiter of the law. Not only is this excessive, but it's anti-customer.

If DO is doing what they think they must by law, I have no problem with that, as long as that is clearly explained. In the case we were previously talking about, the statement from DO (at the motherboard article) is somewhat ambiguous as to why they did what they did. Per DigitalOcean’s terms of service, a final reminder was issued to our customer and, when no action was taken, access to the content was disabled. Was the take down required by law, or was DO overly aggressive in handling it? Without a statement as to why, (and I think that given some people's assertion that they went beyond what was legally required of them), their reasoning is somewhat ambiguous, and harder to call into question. If they clearly define they enforced their TOS based on what they believe is a legally required of them, then we can look at the law and their actions and evaluate whether that's true, and if it's not, DO can learn from the experience or be called out as a company that is capricious in their execution of the law.

What it boils down to is that "We received a complaint infringement. We enforced our TOS and shut down access to the content in question." leaves a lot open for assumption. I would be much happier if it was "We received a complaint infringement and as we believe is legally required of us we enforced our TOS and shut down access to the content in question." It's a small change, but it allows customers (and critics) a much clearer view on how DO handles situations like this, and allows for the public to make an informed choice on whether they think DO was correct in their actions (whether they really were legally required to do so). It's subtle, but I think it's a very, very important distinction.

Re: Highly Available Block Storage

#145
How is it taking huge cloud providers so long to catch up with things we do self hosted every day? It obviously has to be well engineered, yet it's relatively simple. Woefully poor performance too.
Post reply on HN