Identity in Microservices
Pat discusses the complexities of identity, using ISBNs as an example to illustrate how nuanced it can be when distinguishing between different versions of a book. He emphasizes that in a microservices architecture, the concept of "right" data becomes fragmented, leading to the need for a deeper understanding of both current and historical data states. The conversation highlights the shift from traditional ACID transactions to a more flexible approach in handling data correctness.In this clip
From this podcast
Software Engineering Radio - the podcast for professional software developers
Episode 397: Pat Helland on Data Management with Microservices.mp3
Related Questions