Pros and Cons of using ConcurrencyMode.Multiple in WCF

Question

I am new to WCF. I have a WCF where many application using this service. And my requirement is, WCF service should handle multiple request at the same time. I know that this can be acheived by using [ServiceBehavior(ConcurrencyMode = ConcurrencyMode.Multiple)].

But I want to know what are the pros and cons of implementing Multiple option, as my service deals with payment processing. And I guess default ConcurrencyMode is Single. Can anyone please guide me by your suggestions?

As far as I surfed, everyone suggesting if we use ConcurrencyMode.Multiple, we are responsible for providing the necessary synchronization/thread safety. I am bit confused, what kind of issues may occur and what are the steps needed to overcome when using ConcurrencyMode.Multiple and InstanceContextMode.PerCall?

score 1 · Answer 1 · edited May 23 '17 at 12:15

1

ConcurrencyMode.Multiple can cause scalability issues and may cause threading issues as mentioned in the SO link - ConcurrencyMode.Multiple in stateless WCF services.

edited May 23 '17 at 12:15

Community

1
1

answered Oct 08 '13 at 06:23

Krishna

636
3
8

score 0 · Answer 2 · answered Oct 08 '13 at 13:51

0

I suggest you consider reviewing the following "Concurrency Management" excerpt from the “Programming WCF Services” book: http://msdn.microsoft.com/en-us/library/orm-9780596521301-02-08.aspx

answered Oct 08 '13 at 13:51

Seymour

7,043
12
44
51

score 0 · Answer 3 · answered Oct 08 '13 at 13:56

The following articles might provide more information on the subject...

http://blogs.msdn.com/b/rickrain/archive/2009/06/15/wcf-instancing-concurrency-and-throttling-part-1.aspx

http://www.codeproject.com/Articles/89858/WCF-Concurrency-Single-Multiple-and-Reentrant-and

Pros and Cons of using ConcurrencyMode.Multiple in WCF

3 Answers3