Oh really? BDR is acid-compliant? How can it be without a global lock manager to control access to resources and a consistent view of data and enforce isolation levels? Please explain the magic. On Wed, 24 Nov 2021 at 14:03, MichaelDBA <MichaelDBA@xxxxxxxxxxx> wrote: You do understand that multi-master replication is not acid-compliant and the implications of that, right? It only works well for "read globally, write locally" scenarios. This isn't true. Async multi-master has performance advantages, but some drawbacks. But systems such as BDR3 allow multiple modes of operation that overcome these perceived issues. Holger Jakobs wrote on 11/24/2021 12:08 PM: On Wed, 24 Nov 2021 at 14:03, MichaelDBA <MichaelDBA@xxxxxxxxxxx> wrote:You do understand that multi-master replication is not acid-compliant and the implications of that, right? It only works well for "read globally, write locally" scenarios.This isn't true. Async multi-master has performance advantages, but some drawbacks. But systems such as BDR3 allow multiple modes of operation that overcome these perceived issues. |
