Event-Driven Microservices need to materialize states. And it comes with the important things to think about. Two approaches to choose from:
Internal state store or External state store Both have pros and cons. Both have important scalability and recovery considerations.
Two approaches for changing data structures:
Bebuilding and Migration Transactions and how to emulate them in order to implement Effectively Once processing.
All of these is disclosed in the Chapter 7 of the book we are currently studying:
There is quite a high demand for blockchain development these days. We do some experience with it as a company (one complex multi-year project), but personally I only had high-level knowledge and I wanted to improve it…
Earlier the book club of our company has studied excellent book:
Martin Kleppmann - Designing Data-Intensive Applications
This is the best book I have read about building complex scalable software systems. 💪
As usually I prepared an overview and mind-map.
Chapter 12 is a summary of the book and a visionary view of the future.
Data Integration. Overview of the ways we have to integrate data. Causality and why we need Total Order and Idempotency.
Earlier the book club of our company has studied excellent book:
Martin Kleppmann - Designing Data-Intensive Applications
This is the best book I have read about building complex scalable software systems. 💪
As usually I prepared an overview and mind-map.
Chapter 7 is all your DEV team should know about Transactions:
The purpose of transactions The concept of transaction: ACID, BASE, single-object and multi-object transactions Weak Isolation Levels: Read Committed, Snapshot Isolation and Repeatable Read.
