Real-world consistency explained
Uwe Friedrichsen explores the challenges, options, and trade-offs of different consistency models in distributed system landscapes, covering the limitations of ACID transactions, eventual consistency, and current research that tries to fill the gaps between ACID and BASE transactions.
| Talk Title | Real-world consistency explained |
| Speakers | Uwe Friedrichsen (codecentric AG) |
| Conference | O’Reilly Velocity Conference |
| Conf Tag | Build Resilient Distributed Systems |
| Location | London, United Kingdom |
| Date | October 18-20, 2017 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
Here we are: microservices, containers, the cloud. . .and lots of data to deal with. Usually, that’s where the real trouble starts. Many developers still base their designs on the concept of perfectly consistent ACID transactions, with no anomalies or other inconsistencies to speak of, but reality is different. Perfect consistency does not exist, and many real-world use cases require much weaker consistency models in order to satisfy the scalability or robustness requirements. So what are your options, and what price must you pay? Do you need to accept potentially losing data in order to get higher availability? How much can you scale without compromising consistency? Uwe Friedrichsen explores the challenges, options, and trade-offs of different consistency models in distributed system landscapes, covering the limitations of ACID transactions, eventual consistency, and current research that tries to fill the gaps between ACID and BASE transactions. Along the way, Uwe explains how to pick the right data store (not only) with respect to consistency.
