Nice explanation, please keep creating this type of content, very neat and to the point.

loved this explanation!

Nice one

How to handle deadlock situation in such case?

What are some other solutions for a similar problem?

be regular

Instead of having each seat as a row in the database and using locks, we can use a saga pattern. As part of the transaction, we will decrease the availability (of seats or products). If the transaction fails down the line (failure in payment), we can implement a compensating transaction which will increase the availability by the same amount. What do you think?

@Adi-yi6qq

5 ай бұрын

This does not solve the problem of double booking though.

@gopalchakraborty5834

Ай бұрын

Saga pattern is built for breaking down a long transaction into small transaction and commit in every step until and unless all the smaller transaction is successful the final commit will not happen .it could not help with validate the concurrent booking for a shared resource.

Very nice info. Thank you for sharing. What's the software you're using for presentation.

@LeoLeo-nx5gi

Жыл бұрын

excalidraw