Wcf concurrent requests

Question

1.00/5 (1 vote)

See more:

I have to develop a banking system which allows users to deposit or withdraw in accounts.
I have implemented the whole logic,now the requirement is that an account cannot have negative balance,I am stuck here.

Multiple users can with-draw from a single account. How can I implement the negative balance in-case of multiple concurrent users(or requests)?
eg User A and B with-draws at same time, User A's request finish first and the account got negative balance,then how can I give error to user B?

What I have tried:

I have created WCF Restful service with two methods for deposit and withdrawal. I am checking account balance while with-drawing.

Posted 7-Jun-17 9:24am

Member 13246559

Updated 9-Jun-17 9:28am

Add a Solution

Comments

Afzaal Ahmad Zeeshan 7-Jun-17 15:48pm

Then that is the part of the data layer, where you make sure that the data with negative values never gets stored. What is wrong?

Also in the case where multiple users are connecting and performing some tasks on the data source, make sure you are implementing any mechanism of locks, so that only one account (or user, or thread, or process) can access the content. Otherwise data might be left inconsistent.

Member 13246559 7-Jun-17 16:20pm

Can you please provide some sample code for this?

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)

cjmakwana · Answer 1 · 2017-06-09T09:28:00

As Afzaal pointed out, you need to wrap your each transaction inside a unit-of work and lock it, to make it truly ACID transactions. At the end of each transaction, you need to watch whether the balance has reached below specified value (or negative). Even though there is concurrency, the subsequent transactions will wait until the current is finished.