do you need a distributed transaction? working through a design problem
Published 1 year ago • 13K plays • Length 12:45Download video MP4
Download video MP3
Similar videos
-
12:03
avoiding distributed transactions with the reservation pattern
-
13:06
how to do distributed transactions the right way? microservices
-
31:10
do you know distributed transactions?
-
4:08
orchestration design pattern | distributed transaction management| microservice design patterns
-
7:23
distributed transactions: don’t use them for microservices
-
26:47
event-driven architecture: i do not think it means what you think it means
-
25:49
solving distributed data problems in a microservice architecture | microservices.io
-
7:59
the saga pattern in microservices (eda - part 2)
-
21:54
2 phase commit for distributed transaction management in microservices | code decode |
-
29:31
a different flavor of the distributed transaction
-
8:52
data consistency between microservices
-
43:27
20. handle distributed transactions | two-phase commit (2pc), three-phase commit (3pc), saga pattern
-
6:48
the saga design pattern explained in 6 minutes | orchestration vs choreography
-
13:08
sharing a distributed computing system design from a real software problem
-
9:10
reliably save state & publish events (outbox pattern)
-
10:34
challenges of acid transactions in a distributed database
-
14:47
discover a distributed big ball of mud with distributed tracing
-
11:49
rest apis for microservices? beware!
-
9:48
handling failures in message driven architecture
-
9:01
highly cohesive software design to tame complexity