> 99% of their SQL databases probably don't require transactions and ACID behaviour 99% of applications do not require multi-statement transactions or rollback

> 99% of their SQL databases probably don't require transactions and ACID behaviour 99% of applications do not require multi-statement transactions or rollbacks, but basic ACID is hard to live without (at least the 'D' and 'C' parts). You probably don't need a massively parallel transaction system, perhaps you just need to isolate writers out but the fact is that most of what you need comes for "free" with a standard SQL database + failovers. It's not that no one was fired for picking it, but that people can be hired to fix it when it doesn't quite work as well as it should.