The Hardest Part of Microservices - Your Data

This talk explores data ownership and transaction boundaries in microservices, using domain-driven design concepts such as entities, aggregates, and bounded contexts. It discusses consistency and failure tradeoffs and demonstrates an example using Apache Kafka, Apache Camel, and Debezium.

Syllabus

Introduction
Slide deck
Christian Posta
Adrian Cockroft
Optimizing IT
Optimizing for speed
Managing dependencies
What is data
What is one thing
Book example
Domaindriven design
Normalization
Acid
Comfort
Issues
We have to
fully data centric
what what
data inside my service
data outside my service
point in time snapshot
call graph
time
reading data
failures
coordination
microservices
when things fail
if youre not careful
the NN1 problem
caching
the cap theorem
consistency
baseball consistency
relaxed consistency
Strict consistency
Manage the data
The BGM
How it works
Cache catchment
Bounded contexts
Microservice architecture
Demo Java EE
Learnings
Demo