How transaction is made for single user where multiple users try to book tickets online for same seat ?

Question

1.00/5 (1 vote)

See more:

how to handle such situation.if two seats are available.10 different people were trying to book tickets for those two seats .then finally seats booking is done for only single person and how transaction is managed.

What I have tried:

i thought its using lock concept as iam not much familier to this kind of scenarios .i hope you would help me.

Posted 7-Feb-18 21:35pm

saimanisha

Updated 7-Feb-18 22:45pm

v2

Add a Solution

Comments

Ziee-M 8-Feb-18 4:36am

This is actually a concurrency situation. Concurrency occur when more then one transaction tries to update the same row/data.
An exception will be raised if you fall in this case and you have to handle that exception to resolve the situtation.
I cant Give you more details because it totaly depend on the tools you use to access your database (EnityFrame, ADO.net...)
Each one of these handle the Concurrency diffrently.
Just a few searchs with concurrency keyword, and you will find a lot of answers.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

F-ES Sitecore · Accepted Answer · 2018-02-07T22:28:00

Solution 1

The record for the seat in the database should have some kind of "locked at" field. When someone clicks the "book" button it will update the "locked at" field with the current time. If someone else tries to book a seat with a non-null locked time they're told someone else is booking it. When the user cancels the booking then clear the field, you could also clear it when the booking is made. The tricky bit is that you then need some form of automated task (SQL agent, scheduled task, windows service, timed event etc) that clears locks that are over, say 10 minutes old and assume the booking was just abandoned.

Posted 7-Feb-18 22:28pm

F-ES Sitecore

Comments

Ziee-M 8-Feb-18 4:57am

I dont think this is a practical solution, many other users will be blocked while the first one is buying. In addition, the Booking process can take several minutes.

F-ES Sitecore 8-Feb-18 5:04am

The alternative is to let the other users go through that 7 minute process simply to be told at the last second that someone else got the seat. They might then search for another seat and have the same thing happen so simply abandon your site altogether.

Ziee-M 8-Feb-18 5:10am

I think you just add a trigger that raise an exception in Database level when no tickets are left. and you have to manage concurency in a hight transaction environement like this one.