BackendDatabases
Two-Phase Commit
Also written as 2PC
A protocol for making several systems commit a change together or not at all. Correct in theory, but it stalls everyone if any participant goes quiet.
Think of it like
Everyone signing a contract in the same room. Watertight, and completely stuck if one person steps out.
Junior or senior?
Mentioning it is fine. Knowing why most modern systems avoid it in favour of the saga pattern is the actual signal.
Ask them
“When would you choose a saga over a distributed transaction?”