CODEWITHSUNDEEP
transactionscqrs
Golo Roden
Golo Roden

Reputation: 150624

"two-phase commits [...] always cause problems in the long run" - why?

In the CQRS Journey, Chapter 5 there is an imaginary dialog called Pushing changes from the Conference Management bounded context between two developers. They are discussing the transaction options in a CQRS architecture to have saving and publishing events bound together. In the 4th paragraph from the end, developer 2 says:

"Second, we're trying to avoid two-phase commits because they always cause problems in the long run."

I was wondering why this is.

Can anyone elaborate?

Upvotes: 1

Views: 148

Answers (1)

Golo Roden
Golo Roden

Reputation: 150624

A nice explanation is given in Your coffee-shop does not use 2PC: Baically it comes down to bad scalability due to waiting when synchronizing.

Upvotes: 1

Related Questions