What's amazing is that 3 terabyes costs about $300 nowadays. Include good components, power, redundancy, maintenance, and it probably comes to $1,000 per year.
So this feature is actually pretty cheap to do, unless I'm missing something.
Every time I read "terabyte", I have to pause, because my brain goes "That's gigantic!" and then a little voice says, "It's the same size as the hard disk in my desktop...it cost $89."
I have the same sort of weird mental disconnect with SD cards. It's just hard to fathom 32GB of data fitting into something about the size of a quarter.
Hey, I know the feeling, it's weird to adjust to but I still haven't filled my 5 Terabytes of space yet so I'm happy. Soon I'm going to offload all my files to a file-server I'm building with an exorbitant amount of HDD space.
Serving up thousands of requests per seconds from 3 TB (while continually adding and updating more data!) is a lot different from just archiving it.
A _lot_. :)
To put it in perspective, 100GB is pretty much the limit of what you can serve from a single mysql machine, for instance. This will vary depending on exact workload but that is a reasonable ball park number.
Of course, in a relational database you wouldn't (generally) be storing the vast majority of the data in question...you'd be querying for it. That's not to trivialize the improvement in performance here, just to point out that this probably would be 100GB in a MySQL database.
So this feature is actually pretty cheap to do, unless I'm missing something.