4 ms·

It looks like the most recent data point, S3 was actually cheaper than the raw storage, while providing 11 9's of durability, across multiple AZs. Still looks

by influx 4y ago

It looks like the most recent data point, S3 was actually cheaper than the raw storage, while providing 11 9's of durability, across multiple AZs. Still looks like a pretty good deal, as the price of storage has mostly flatlined in this graph. Nor does this even account for cold storage, or reduced redundancy.

secabeen 4y ago
The prices are in different units. S3 is $/GB-Mo, raw storage is in $/GB. So, when they are equal on the graph, you are paying each month to AWS what the cost of the raw disk is. Now, yes, you need a lot more than just raw disk to effectively store data, but even if you just assume a 5-year lifespan for that disk, the price difference displayed on the graph as equality is actually a 60x difference in plain $. The price has also appeared to flat-line because they are using a linear graph scale for logarithmic data. It should use a log-scale for the y-axis.
- ceeplusplus 4y ago
  Now factor in redundancy and server costs, and the difference is not so huge. You're still paying a multiple of the raw cost, but unless you're storing on the exabyte scale I think it shouldn't really matter in the grand scheme of things. Cost of a single engineer to manage a Minio cluster probably already outweighs the extra cost you're paying at any reasonable scale (i.e. most companies). And if you're a big player the published costs are not what you're paying.
  - hedora 4y ago
    They use wide erasure code stripes, so redundancy is ~ 1x within a data center. Let's assume 3 data centers. It's well known how to build a storage node whose cost is mostly disks, let's say 50% of the hardware is not disks. So, redundancy and server costs explain up to a 6x mark up. Power and networking really shouldn't account for the other 54x.
    - jenny91 4y ago
      I agree with you but if you explain the 6x mark up, you only have 10x to explain out of 60x.
      - hedora 4y ago
        It depends on if you're comparing to raw disk, or the replicated storage, but yeah, spending 9x more on network and power than on machines is still pretty extreme.
    - Sebb767 4y ago
      You also need to house these servers, including backup power etc., manage them, maintain them, develop and deploy the software etc.. Also, you should really check the power usage of enterprise disks and servers; it may be cheap, but it's far from comparable to your average desktop. Then you need to add in that they need to have a reserve capacity as well; you can now go and store 100TB on S3 and AWS will be fine with it - but they need to have those disks up & running already. Don't get me wrong, S3 is expensive, but replicating the availability, feature set and scalability is going to be very expensive, too. You can cheap out if you don't need these features, of course.
dahfizz 4y ago
That is the cost per month. Every single month you pay the full cost of the hardware you use. The real killer on S3 is bandwidth anyway. Getting your data out of S3 costs much more than leaving it there, which I'm sure is by design.

by influx 4y ago

secabeen 4y ago

The prices are in different units. S3 is $/GB-Mo, raw storage is in $/GB. So, when they are equal on the graph, you are paying each month to AWS what the cost of the raw disk is. Now, yes, you need a lot more than just raw disk to effectively store data, but even if you just assume a 5-year lifespan for that disk, the price difference displayed on the graph as equality is actually a 60x difference in plain $. The price has also appeared to flat-line because they are using a linear graph scale for logarithmic data. It should use a log-scale for the y-axis.

ceeplusplus 4y ago
Now factor in redundancy and server costs, and the difference is not so huge. You're still paying a multiple of the raw cost, but unless you're storing on the exabyte scale I think it shouldn't really matter in the grand scheme of things. Cost of a single engineer to manage a Minio cluster probably already outweighs the extra cost you're paying at any reasonable scale (i.e. most companies). And if you're a big player the published costs are not what you're paying.
- hedora 4y ago
  They use wide erasure code stripes, so redundancy is ~ 1x within a data center. Let's assume 3 data centers. It's well known how to build a storage node whose cost is mostly disks, let's say 50% of the hardware is not disks. So, redundancy and server costs explain up to a 6x mark up. Power and networking really shouldn't account for the other 54x.
  - jenny91 4y ago
    I agree with you but if you explain the 6x mark up, you only have 10x to explain out of 60x.
    - hedora 4y ago
      It depends on if you're comparing to raw disk, or the replicated storage, but yeah, spending 9x more on network and power than on machines is still pretty extreme.
  - Sebb767 4y ago
    You also need to house these servers, including backup power etc., manage them, maintain them, develop and deploy the software etc.. Also, you should really check the power usage of enterprise disks and servers; it may be cheap, but it's far from comparable to your average desktop. Then you need to add in that they need to have a reserve capacity as well; you can now go and store 100TB on S3 and AWS will be fine with it - but they need to have those disks up & running already. Don't get me wrong, S3 is expensive, but replicating the availability, feature set and scalability is going to be very expensive, too. You can cheap out if you don't need these features, of course.

dahfizz 4y ago

That is the cost per month. Every single month you pay the full cost of the hardware you use. The real killer on S3 is bandwidth anyway. Getting your data out of S3 costs much more than leaving it there, which I'm sure is by design.