<story><title>Wasabi – Simple storage solution</title><url>https://wasabi.com/product</url></story><parent_chain><item><author>knobbytires</author><text>Some quick observations:&lt;p&gt;- Their performance claims are incredibly biased. Amazon S3 has far better write performance than their claims.&lt;p&gt;- 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 and DELETE did work but that is only 3 of 100’s of API’s.&lt;p&gt;- Their durability claims are highly suspect. I would want to see a white paper breaking this down.&lt;p&gt;- Their first round was debt financing.&lt;p&gt;Why this business model does’t work...&lt;p&gt;Most people don’t use S3 alone. S3 is a source for other AWS services. That being said, Wasabi becomes a more expensive option as you have a 4 cent egress fee to access data from the rest of your AWS infrastructure. The only place Wasabi becomes cheaper is for those using S3 direct&amp;#x2F;alone which is a very small subset of S3 usage. AWS is very open about this in white papers, conferences, tech talks, etc.&lt;p&gt;Wasabi is an economy at scale play that cast way too far a net. There is opportunity in specific vertical markets to sell a solution (object paired with compute) but a pure S3 endpoint will never take substantial marketshare away from AWS.</text></item></parent_chain><comment><author>gaul</author><text>&amp;gt; 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 and DELETE did work but that is only 3 of 100’s of API’s.&lt;p&gt;Validating claims of S3 compatibility is important.  The S3 API has corner cases like and misfeatures like BitTorrent hosting but sometimes vendors omit key features like multi-part upload and v4 signatures.  s3-tests[1] is the best way we have to evaluate implementations yet only Ceph and S3Proxy seem to contribute to it.  Users should hold vendors&amp;#x27; feet to the fire about these these claims.&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;ceph&amp;#x2F;s3-tests&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;ceph&amp;#x2F;s3-tests&lt;/a&gt;</text></comment>
<story><title>Wasabi – Simple storage solution</title><url>https://wasabi.com/product</url></story><parent_chain><item><author>knobbytires</author><text>Some quick observations:&lt;p&gt;- Their performance claims are incredibly biased. Amazon S3 has far better write performance than their claims.&lt;p&gt;- 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 and DELETE did work but that is only 3 of 100’s of API’s.&lt;p&gt;- Their durability claims are highly suspect. I would want to see a white paper breaking this down.&lt;p&gt;- Their first round was debt financing.&lt;p&gt;Why this business model does’t work...&lt;p&gt;Most people don’t use S3 alone. S3 is a source for other AWS services. That being said, Wasabi becomes a more expensive option as you have a 4 cent egress fee to access data from the rest of your AWS infrastructure. The only place Wasabi becomes cheaper is for those using S3 direct&amp;#x2F;alone which is a very small subset of S3 usage. AWS is very open about this in white papers, conferences, tech talks, etc.&lt;p&gt;Wasabi is an economy at scale play that cast way too far a net. There is opportunity in specific vertical markets to sell a solution (object paired with compute) but a pure S3 endpoint will never take substantial marketshare away from AWS.</text></item></parent_chain><comment><author>tw04</author><text>&amp;gt;but a pure S3 endpoint will never take substantial marketshare away from AWS.&lt;p&gt;Perhaps in the &amp;quot;dev&amp;#x2F;ops&amp;quot; world, but S3 as a standalone repository could absolutely work for most enterprises and quite frankly soho users as a backup target.  That being said, I have almost no faith this will survive and as such wouldn&amp;#x27;t trust it with my backups.</text></comment>