FoundationDB supports its YesACID model with an article
it is better to have application programmers deal with performance problems due to overuse of transactions as bottlenecks arise, rather than always coding around the lack of transactions
It is true that eventual consistency is hard to program against. So relying on transactions can give you a lot less complexity. As soon as you run into consistency problems…
If you offer people database columns, they will create a column with a type for each and every property. If you offer relations, you will get desired relations and every other relation, too. If you give them acid, chances are that we get huge transactions.
As usual you have to pick the right tool for the job. And then you have to have the right people to do the job.

