Managing Consistency, State and Identity in Distributed Microservices

on YouTube ↗39m

" summary

Argues that services must own their hot state and use event sourcing and an append-only event log to make identity composable, auditable and replayable rather than rely on distributed transactions. Recommends local in-memory state, snapshotting, and Akka Distributed Data or polyglot backends (Cassandra, etc.) for replication, using idempotency, causal/eventual consistency and promise-based designs to avoid cross-service obligations. Demonstrates a shopping-cart example where CRUD loses history but the event log preserves every delete so analytics, audits and self-healing reconstruction work.

AI-written summary · about

" chapters (13)

1. 0:00Start
2. 3:37"Traditional Application Architectures and Platforms are Obsolete" -- Gartner
3. 6:21Supports multiple autonomous teams organized to scale the development where the teams can develop, deploy and manage their services independently
4. 7:13A system of autonomous collaborative distributed services
5. 7:36Autonomy From Greek Auto-nomos: auto meaning self nomos meaning law
6. 15:08Consistent State. What about it? Sounds like a problem
7. 16:48One Definition Stateful means the computer or program keeps track of the state of interaction, usually by setting values in a storage field designated for that purpose.
8. 23:52There is no such thing as a "stateless" architecture. It's just someone else's problem of an absolute now
9. 25:03Think in terms of Consistent Boundaries
10. 25:45Bounded Contexts
11. 28:18Composable Identity. The meaning of life?
12. 29:06Polyglot Persistence
13. 29:44"The truth is the log. The database is a cache of a subset of the log." --Pat Helland

" related talks

• 27mData Consistency in Microservices ArchitectureGrygoriy Gonchar · Voxxed Days Microservices 2018
• 51mPatterns & Practices of Implementing Event-driven MicroSvc...Nikhil Barthwal · GeeCON Prague 2023
• 35mConsistent Updates in a Distributed System without TransactionsStefan Richter, Marco Hennings · code.talks 2017
• 01h 11mEmbracing Messaging and Eventual Consistency in your Microservices SolutionsMichele Bustamante · NDC Porto 2019
• 01h 25mBuilding microservices with event sourcing and CQRSMichael Ploed · SpringOne2GX 2015
• 44mBuilding event-driven microservices with Scala and Functional Domain ModelsChris Richardson · Great Indian Developer Summit 2015
• 46mMicroservices architecture and data consistencyJean-François James · DevFest Lille 2022
• 48mIntegrating microservices by accepting the data dichotomyDamien Gasparina · Voxxed Days Microservices 2018