3 ms·
I agree in that they are probably comparing the wrong aspects of S3. You're not going to be able to compete on the speed anytime soon probably, and maybe even
by carlosdp 7y ago
I agree in that they are probably comparing the wrong aspects of S3.
You're not going to be able to compete on the speed anytime soon probably, and maybe even the capacity if it really takes off. But, anyone here that works on an Amazon-based internet company knows that S3 is the most unreliable (in terms of availability, not storage) universally used product they have, next to EC2.
A good chunk of incidents can be attributed to S3 downtime in some AZ. With a decentralized storage network, the probability of actual downtime in terms of availability go wayyyyy down. If Amazon us-east-1 has a bad deploy or a network event, you lose access to those buckets, full-stop.
With something like this, you'd need a much larger network event, and if the app is fully decentralized itself, blast radius can be contained to individual customer regions instead of where you host your servers.
Probably more useful to compare to GCS Storage honestly, since they have multi-region buckets.
- Taek 7y ago> You're not going to be able to compete on the speed anytime soon probably, and maybe even the capacity if it really takes off Sia today running in the default configuration gets as much as 300mpbs upload and download, which I believe is comparable to S3. Latencies are several seconds, which is not comparable to S3 however this is a matter of software optimization, not a fundamental limitation of the network architecture.
- khc 7y ago300mbps is no where close to s3 throughput. Try 300MBps per node and much higher when you access the same bucket in multiple nodes