"Transactions: myths, surprises and opportunities" by Martin Kleppmann

jepsen.io has a neat diagram of various consistency models - link also, you can find talks of Martin Kleppmann on youtube about consistency guarantees, e. g., ▶ this video

I mean, I hear you that people do that and it does allow you to avoid needing distributed transactions. When you're stuck with an underlying NoSQL database without transactions, this is the best thing you can do. This is the whole "invert the database" idea that ends up with [1]. I'm arguing that that usage pattern was painful and that if you can have horizontally scalable transaction processing and a stream of events due to committed transactions downstream, you can use that to power correct and easy to reason about materializations as well as asynchronous task processing. Transact to change state. React to state changes. Prosper. [1] ▶ this video

It's great. Incredibly dense with useful information and it just blows my mind how much knowledge Martin has about the topic. I recommend watching this talk from him to give a little glimpse of the book: ▶ this video This is just about a little part of one of the chapters.

Rich Hickey - "simple made easy" link Rob Pike - "concurrency is not parallelism" link Uncle Bob Martin - "future of programming" link Martin Kleppmann - "transactions: myths, surprises and opportunities" ▶ this video Simon Brown - "software architecture vs code" link