Depending on your access patterns, Backblaze B2 might be cheaper at $0.005/GB stored and $0.02/GB downloaded.
Wasabi – Simple storage solution
81–90 of 164 posts
Re: Wasabi – Simple storage solution
#82Isn't Wasabi a programming language from Fog Creek Software?
It was an in-house compiler that they're not using anymore. https://blog.fogcreek.com/killing-off-wasabi-part-1/
Re: Wasabi – Simple storage solution
#83CTRL+F "availability". 0 results found.
Re: Wasabi – Simple storage solution
#84The article states: "Wasabi’s durability is 11 x 9s, the same as Amazon S3. To put that in context, if you stored 1 million 1 GB files in Wasabi, you would expect on average to lose one file every 659,000 years" Can someone walk me through the math here? I specifically curious about why the size of the file being 1 GB is relevant to the calculation.
It doesn't matter. This is marketing fluff. What companies like Amazon do is count how many hard drives would need to simultaneously fail to lose data, calculate the odds of a hard drive losing data, and then multiplying. This gets you to 11 9's.
In practice, this is almost certainly not going to be why you lose data. That will be because of a chain of human errors, or a code bug, or because the user accidentally deleted the data, or because earthquakes destroyed your data centers.
I don't know anything about Wasabi other than what's on their web page, but I half suspect that what they did was look at Amazon's durability guarantee and then write that number down as their durability guarantee.
Re: Wasabi – Simple storage solution
#85They're claiming the same 11 9s durability that S3 does. I'd be pretty suspicious of that claim without a track record but it looks like Wasabi's founders come from Carbonite. Bring on the competition, commoditization of fundamental building blocks is great for everyone except people trying to make startup-scale returns on them.
Those durability numbers for both Amazon and Wasabi are pure marketing and don't really mean anything even remotely important. Durability of data stored by a single company, even a company like Amazon, is actually very low, you should be scared of how low it really is. You could get kicked out from the service, lose data because of a bug or an operational mistake, be prevented from using the service by your governmen…
You're mixing the technical availability, as in the amount of downtime, with organizational availability, as in your contract being abruptly terminated.
Even with 100% technical availability (no downtime ever), organizational / legal risks exist. No company can realistically be free of them. Amazon, compared to many smaller companies, may have somehow lower risks of this sort: they are hard to shut down.
If you care about your data really much, you likely have backups and / or mirror copies of it across several providers, in multiple countries, and have a well-tested contingency plan to move a complete copy of your production service to any of 2-3 other providers. (And likely most people don't have your risks and the amount of money enabling this all.)
Re: Wasabi – Simple storage solution
#86Earlier quoted context omitted.
does this work with django storages?
No. It uses the OpenStack API. https://github.com/openstack/python-openstacksdk You'd need to use that to build it out.
Probably no need to do this on their own. Found two already existing implementations, and suspect there are more:
Re: Wasabi – Simple storage solution
#87Earlier quoted context omitted.
Those durability numbers for both Amazon and Wasabi are pure marketing and don't really mean anything even remotely important. Durability of data stored by a single company, even a company like Amazon, is actually very low, you should be scared of how low it really is. You could get kicked out from the service, lose data because of a bug or an operational mistake, be prevented from using the service by your governmen…
You're mixing the technical availability, as in the amount of downtime, with organizational availability, as in your contract being abruptly terminated. Even with 100% technical availability (no downtime ever), organizational / legal risks exist. No company can realistically be free of them. Amazon, compared to many smaller companies, may have somehow lower risks of this sort: they are hard to shut down. If you care…
It doesn't make sense to me to think of durability for cloud storage services as anything other than the probability of data retention for a client, which is impacted by your contract being abruptly terminated too, although not by the amount of downtime.
Re: Wasabi – Simple storage solution
#88Earlier quoted context omitted.
Not only. There is also minimum 90-day charge for objects. https://wasabi.com/pricing/pricing-faqs/
According to that, there is an extra "9" they didn't show, so $3.99 rather than $3.90. So then if you deleted your 1TB each month, and uploaded new data, you'd be paying 3 times more due to the 90 day minimum charge, so about $12/month in the worst case.
They're using 1TB as in 1024GB. 1024*$0.0039 = $3.9936
Re: Wasabi – Simple storage solution
#89Wouldn't it be funny if this was just a market test/exercise, using actual S3 as a backend, just to see if it gets any traction before building own HW/SW solution?
Could explain the 1tb minimum. Hoping most people don't get close to it.
Re: Wasabi – Simple storage solution
#90Some quick observations: - Their performance claims are incredibly biased. Amazon S3 has far better write performance than their claims. - They claim 100% S3 compatibility but it fails a large number of API calls using Ceph’s s3-test. I didn’t dig into this too far but they do claim “No need to change your S3-compatible application” so changing my endpoint + credentials should have worked. To their credit - PUT, GET…
Yes, it's hard to find use cases where Wasabi storage could compete without compute. But S3 originally launched by itself, before EC2. If Wasabi adds a Lambda-like serverless compute layer that could be powerful.
Also you can change your s3 bucket to enable multi-factor delete, which essentially makes it immutable unless you delete using a 2fa device, which shouldn't really happen accidently.