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

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" [VIDEO] Simon Brown - "software architecture vs code" [LINK]

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: [VIDEO] This is just about a little part of one of the chapters.

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] [VIDEO]

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., [VIDEO]