Using sagas to maintain data consistency in a microservice architecture

local transactions
https://youtu.be/YPbGW3Fnmbc?t=1043
local compensation transactions
https://youtu.be/YPbGW3Fnmbc?t=1241
cases of transactions rollback
https://youtu.be/YPbGW3Fnmbc?t=1408
complications with sagas
https://youtu.be/YPbGW3Fnmbc?t=1661
Choreography model
https://youtu.be/YPbGW3Fnmbc?t=1805
Coordinator model
https://youtu.be/YPbGW3Fnmbc?t=1837
https://youtu.be/YPbGW3Fnmbc?t=1883 (state machines)
https://youtu.be/YPbGW3Fnmbc?t=1938 (implicit and explicit orchestrate)
https://youtu.be/YPbGW3Fnmbc?t=2011 (event bases implicit orchestrate)
https://youtu.be/YPbGW3Fnmbc?t=2111 (explicit orchestrate)
https://github.com/eventuate-tram/eventuate-tram-sagas-examples-customers-and-orders
https://youtu.be/YPbGW3Fnmbc?t=2629 (atomic messages)
https://youtu.be/YPbGW3Fnmbc?t=2788 (transaction log tailing)