Well, not so many people use serializable in their systems (in the whole system, for every transaction) and that is common and reasonable approach. They use the

Well, not so many people use serializable in their systems (in the whole system, for every transaction) and that is common and reasonable approach. They use the minimal isolation level for particular transaction that keeps their data consistent. Most widely used safe default is repeatable read, in PostgreSQL terms. Broadly speaking, of course there are some quirks in the field, let's start from "A critique of ANSI SQL isolation levels"[1] by Jim Gray et al., an author of highly respected fundamental book about transactions [2]. But the very kind of problems discussed in RDBMS world, is a rather contrasting with an "ACID? why do we need it?" attitude that is so often in the world of "web scale NoSQL". [1] http://dl.acm.org/citation.cfm?id=223785 http://dl.acm.org/citation.cfm?id=223785 [2] https://www.amazon.com/Transaction-Processing-Concepts-Techniques-Management/dp/1558601902 https://www.amazon.com/Transaction-Processing-Concepts-Techn...?