Uwe Friedrichsen, CTO of codecentric, speaks of Microservices, containers, cloud and lots of data to deal with saying that that’s where the real trouble starts. He shows us what our options are and what the price is that we need to pay.
Uwe thinks that many developers still base their designs on the concept of perfectly consistent ACID transactions, everything being always consistent and in order, no anomalies around. 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 our options and what is the price we need to pay? Do we need to accept potentially losing data in order to get higher availability? How much can I scale without compromising consistency?
In this presentation Uwe answers these questions and also has a look at some popular data stores and examines what kind of consistency models one can achieve with them and how. At the end, he gives us a peek into latest research and new ideas that might push the borders of the current state-of-art.