Dirty read due to concurrent request

Question

1.00/5 (1 vote)

See more:

, +

I have one api.. that is been called by multiple applications through azure logic apps. There is one scenario..The applications which are calling api sometime process concurrently due to which some dirty read happens in api business logic. The request should be processed sequentially, but here in this case(concurrent calls) giving issue. Is there any solution to handle this.

Note : we can implement Azure service bus but for now, we don't want to use that because multiple applications are calling api, so they need to change on their end too.. is there any solution that we can handle only on our end.(API Level) Any suggestions.

Please respond..Thanks :-)

Azure,Asp.Net core

What I have tried:

Throttling will not solve this as there will no. of requests. It will slow down.

Posted 1-Dec-20 14:34pm

Prasad Nikumbh

Updated 6-Dec-20 13:37pm

v3

Add a Solution

Comments

[no name] 2-Dec-20 12:12pm

Then use pessimistic locking. Or are you looking for a "no code" solution. (They don't exist).

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)

CHill60 · Answer 1 · 2020-12-04T01:54:00

You state there are dirty reads in your business logic - which sounds strange. But as you have tagged your question "SQL" then make sure you have the correct isolation level set. Committed reads is the default but you can ensure it is on with

SQL

SET TRANSACTION ISOLATION LEVEL READ COMMITTED

at the head of your query.

By the way, SQL is normally very good at handling concurrency so the problem is most likely to be in the way you have implemented your API.

You could consider queuing the requests into your API - this would be invisible to your callers, but may result in a performance hit (unless you have many listeners in place - back to square 1) - have a look at Amazon Web Services Simple Queue Service Using the Java 2 Software Development Kit[^] or Message Queue[^]. IBM also have a good offering but we're starting to talk some serious money now.

As to your comment about throttling slowing things down - that is what it is meant to do! However, your requirement

Quote:
The request should be processed sequentially,

will have the same effect