> For many years, database users did not have to simultaneously understand the concept of isolation levels and consistency levels This statement might technica

> For many years, database users did not have to simultaneously understand the concept of isolation levels and consistency levels This statement might technically be true, but it hasn't been the case for many years, including much of the time that "CAP Theorem" has been a part of popular discourse in industry. If you take a traditional RDBMS with ACID transactions and ANSI defined isolation levels such as Postgres without extensions (single master) you can still have inconsistent reads if your architecture includes async streaming replicas used for distributing reads. This feature was added in version 9.0 - 10 years ago. Microsoft SQL Server had it at least a decade before that.