Super Simple Storage Service
supersimplestorageservice.com
supersimplestorageservice.com
They give the cost as $211,172, but that's the cost to buy a 1 TiB pack of floppies. Their own storage cost is per-month, so to get the equivalent cost for floppies you need to also divide by the expected useful lifetime of a floppy disk. I did a web search for "floppy disk lifetime" and the internet [1] told me "I’ve seen numbers saying the lifespan of floppy disks is three to five years. But I’ve also seen numbers that claim they can last ten to twenty years or even indefinitely."
If you assume floppy disks have an expected lifetime of 5 years, you can amortise the cost across that time, bringing the cost per TiB-month down to a nice reasonable $3,520.
Going by gut feel: 3-5 years sounds like "pretty likely", let's give that 95% of the weight, at 4 years for simplicity. 10-20 years would be nice, but really, how much tech lasts that long? Not much. How about 4.9999999% at 15 years. And the remaining can go to "indefinitely", which seems pretty darn unlikely, so it has 0.0000001% weight.
(4*95+15*4.9999999+∞*0.0000001 / 100) = ∞
I guess we can ignore the monthly cost ¯\_(ツ)_/¯ I applied weights to things, so this is Bayesian, and we all know that's always right.
Plus, when you’re done writing your data, you’ll have a fancy drink coaster!
There may also be no need to purchase more than one disk. In fact taken to its logical conclusion there is no need to purchase any disk at all - but of course that brings us all the way to the S4 business model itself.
You've got to wonder how it would work if taken to the extreme: rack after rack of floppy drives filling an entire data centre providing a glacially-slow S3 service.
Can you imagine the noise? It would be... glorious.
The linked article used these compact drives: https://www.amazon.com/External-Floppy-1-44MB-FDUSB-M-V1/dp/...
They're 5.75 x 4.25 x 0.75 inches. So if you mount them vertically like in high-density storage arrays, you can fit 25 of them into the width of a rack, about 7 rows from the front to back. So... about 175 per layer that is about 4 RU high including the space for the controller board. You can fit 10 of these layers in a standard rack, for 1,750 floppy drives total per rack.
Let's see... that's 2.52 GB per rack! Seek times are variable depending on the floppy drive model, but 250 ms is approximately correct for the average. So about 7,000 IOPS total per rack. Not too shabby!
A decent sized data centre might have 1,000 racks. So a "cloud-scale" floppy drive object storage system might have 2.52 TB of raw storage. However, you have to divide that by three for the redundant copies, so we're back to 840 GB of usable storage capacity per floor, but with an impressive 7M IOPS.
To put things in perspective, that's directly equivalent to a single modern laptop SSD drive in terms of both capacity and IOPS. Except that the latency of the SSD is 5000x lower.
But a 1 TB HDD and an associated Linux system would probably cost about 300 USD.
Assuming a lifespan of about 7 years, monthly cost comes to about 3 USD per month.
And double all that if you want redundancy.
But the abacus beads could store rotational data. There's at least 8 bits of data there, more if you can put some time in. That's free real estate there.
Well, I see the Dropbox joke here but the service in question is most faithfully replicated with the '> /dev/null' command. Nothing to purchase here.
Durability is one of the headaches you can ignore with a write only interface.
This is a write-only resource…
Now, you could in theory store SHA hashes on a block chain to confirm that the files were written.
Reliably deployed in production for many years at all Fortune 500s!
Tho seriously the lack of a an IaC option means that's a hard no from me. If I can't self-host this on an on-promise open source deployment, they're just making money of people too lazy to set this up themselves with rsync and bash scripts.
The resource cannot be read
The resource you are trying to access cannot be read, due to the following reason:
No read operation available.
Lol... yell in an empty room.
...and then I clicked on the PayPal link :)
> Key Scenarios: Customer complaint database Covert government document storage SETI@home output recorder Personal diary entries Unpublished manuscripts
> Case Studies MotherInLawPhotos.com
https://en.wikipedia.org/wiki/Write-only_memory_(engineering...
http://www.supersimplestorageservice.com/payments/submit/s4/...
Which is actually a custom 403 page made to look like an old IIS error page. if you put in any url on the domain where the file does not exist you get the same error eg
2. Click the buy buttons and then read carefully.
Super Simple Storage Service, huh.
Opinion: This was posted ~10 days late.
This comment started as a joke and now I’m genuinely thinking about it; also from the disk usage claims which make it clear they’re not storing the data, would a service like require a BAA? It’d have to be encrypted at rest, so assuming that was true, and assuming that the data actually got stored (presumably as cold storage) I’m thinking it’d still require BAAs…
What a delightful bit of whimsy.
Always cracks me up, never gets old.
http://www.rfcafe.com/miscellany/cool-products/images/signet...
By the way the upload example form is broken, making it actually work would be awesome
Given that 98% of resumes don't need to be read, this seems like a sane default.
Obviously, they should include "Trash bin" in the pricing comparison table.
S4 costs about the same as S3 Deep Archive storage.
Update: The article appears to be a joke. That aside, there are no cost savings against S3 Deep Archive; additionally S3 Deep Archive supports restores unlike the write-only S4.
I bet that a Super service like this may also support restores, but because of security reasons, they would only be internally and not be visible to the end user.
There is a reason why storage is hard and why I only trust big techs to do it
It's hard to remember now, but there was a period of time not long ago when "the cloud" hadn't yet become an overused catchphrase. In those heady days of yore, people used to store things themselves – usually only on one device, and uphill both ways. These were hardscrabble people, living off of whatever meager storage they could scrounge together. They’d zip things, put them on zip drives, and hope for the best. Then one day almost everyone looked up towards the metaphorical sky and made a lot of compromises.
(In case you completely missed it, this site is satire, similar to /dev/null-as-a-service, etc)
Read time for me has been measured in minutes or sub hour, but the data isn’t huge.