Presentation: Data Consistency in Microservice Using Sagas
Abstract
The services in a microservice architecture must be loosely coupled and so cannot share database tables. What’s more, two phase commit (a.k.a. a distributed transaction) is not a viable option for modern applications. Consequently, a microservices application must use the Saga pattern, which maintains data consistency using a series of local transactions.
In this presentation, you will learn how sagas work and how they differ from traditional transactions. We describe how to use sagas to develop business logic in a microservices application. You will learn effective techniques for orchestrating sagas and how to use messaging for reliability. We will describe the design of a saga framework for Java and show a sample application.
Similar Talks
Stateful Programming Models in Serverless Functions
Principal Engineering Manager @Microsoft, helping lead the Azure Functions Team
Chris Gillum
Evolution of Edge @Netflix
Engineering Leader @Netflix
Vasily Vlasov
Future of Data Engineering
Distinguished Engineer @WePay
Chris Riccomini
User & Device Identity for Microservices @ Netflix Scale
Senior Software Engineer in Product Edge Access Services Team @Netflix
Satyajit Thadeshwar
Observability in the Development Process: Not Just for Ops Anymore
Cofounder @honeycombio
Christine Yen
Data Mesh Paradigm Shift in Data Platform Architecture
Principal Technology Consultant @ThoughtWorks
Zhamak Dehghani
Scaling Patterns for Netflix's Edge
Playback Edge Engineering @Netflix
Justin Ryan
Architectures Panel
Playback Edge Engineering @Netflix
Justin Ryan
Secrets at Planet-Scale: Engineering the Internal Google KMS
Software Developer @Google