7 ms·
I think you’re being too harsh on yourself, isolation levels don’t typically account for replication lag and network partitioning into account. For example on M
by Spivak 4y ago
I think you’re being too harsh on yourself, isolation levels don’t typically account for replication lag and network partitioning into account. For example on MySQL you can have async replication and serializable isolation. Replicas in this mode might never receive updates.
- benbjohnson 4y agoIsolation levels in ACID are typically used for single instances. However, if you're talking about a distributed system then consistency diagram on Jepsen is more applicable[1]. Raft, for example, can ensure read consistency across a cluster by running reads through the consensus mechanism. LiteFS aims to be the analogue to Postgres/MySQL replication and those generally work great for most applications. [1]: https://jepsen.io/consistency https://jepsen.io/consistency