Lost In Transaction? Strategies To Manage Consistency In Distributed Systems

In distributed systems you are in charge of dealing with consistency yourself. ACID transactions are only available locally within components and two-phase commit doesn’t scale. In this talk I discuss these problems and discuss recipes and frameworks, including the Saga-Pattern. Expect fun little live hacking sessions with open source components, but also real-life stories.

Target Audience: Architects, Developers
Prerequisites: Basic knowledge in microservices or distributed systems
Level: Practicing

Extended Abstract
You probably work on a distributed system. Even if you don't yet face a serverless microservice architecture using fancy NoSQL databases, you might simply call some remote services via REST or SOAP. This leaves you in charge of dealing with consistency yourself. ACID transactions are only available locally within components and protocols like two-phase commit don’t scale. Many projects either risk adventurous inconsistencies or write a lot of code for consistency management in the application layer. In this talk I discuss these problems and go over possible solutions, including the Saga-Pattern. I will discuss recipes and frameworks that ease the management of the right level of consistency. This allows you write business logic code. Expect fun little live hacking sessions with open source components, but also real-life stories.