The relevant table is on 27. page.
In short: if you use the SSD in a cold environment AND store it in hot environment than you may lose data quite quickly. Quicker than two weeks.
Client drives are also affected, but the data loss occurs slighly later. I guess reason of the difference is that enerprise drives assume a higher work temperature.
So the advice is that if you use the SSD in your air conditioned basement in a good case then do not store your SSD on the sun for extended periods.
And no, I do not use spinning media as a backup. I use tapes. Using spinning media for proper backups is almost impossible. See http://www.taobackup.com/
I do not understand this complaint about unix configuration either. I am a relatively new Linux user (about 5 years, compared to 20 years on Windows), and I find the Unix configuration system is far-far better than the mess in Windows. Everything is in the
Text configuration files are easily managed by standard command line tools, including diffing and merging changes during upgrade, and non-interactive modifications.
So, when you have an operation and they wind up performing a sex reassignment surgery instead of an appendectomy due to the lack of atomicity, consistency, isolation and durability in their database, you would be OK with it?
Demagogy. Your example has nothing to do with ACID. Such a case would inditate wrong data entry or a client software bug.
By the way, such errors do occur. Even in systems where the database is ACID.
I have not read the article, but I guess they store either very frequent data (measurements) in NoSQL, or large data (3D images). Depending on nonfunctional requirements, neither is possible at all, or cost-effective with RDBMS.
Again we could get infinite scalability with Cassandra for free.
No, no, it is the Apacha Foundation.
I believe you make my point stronger by showing that even with such small resources and incompetent developers, it was possible to create the most moddable game (ever?). Without actually putting any effort into moddability... That made it possible to spend all of their limited resources on a good game design. That is not a small feat.
I worked in both C and Java for many years, and regarding moddability, no, it is not possible to beat Java using C with equal resources. My son's code regurly replace builtin Minecraft classes, runtime, without a significant effort, if the existing extension system does not provides (yet) the necessary hooks for him.
What we would indeed need, is the multi-datacenter capability. Which you get for free with Cassandra... We also sorely needed performance a few years ago (15k SAS drives was slow after an internet hiccup for example), but SSD drives helped in that. Again we could get infinite scalability with Cassandra for free.
You must choose in such a situation: either the - only theoretically needed - ACID, or the actually performing and highly available NoSQL with its additional operations, coding burden?