<p>Does anyone have any experience with how well web services build with Microsoft's WCF will scale to a large number of users?</p>

<p>The level I'm thinking of is in the region of 1000+ client users connecting to a collection of WCF services providing the business logic for our application, and these talking to a database - similar to a traditional 3-tier architecture. </p>

<p>Are there any particular gotchas that have slowed down performance, or any design lessons learnt that have enabled this level of scalability?</p>

[{'answer_id': 43829, 'author': 'aku', 'author_id': 1196, 'author_profile': 'https://Stackoverflow.com/users/1196', 'pm_score': 2, 'selected': False, 'text': '<p><a href="http://weblogs.asp.net/paolopia/archive/2008/03/23/wcf-configuration-default-limits-concurrency-and-scalability.aspx" rel="nofollow noreferrer">WCF configuration default limits, concurrency and scalability</a></p>\n'}, {'answer_id': 47083, 'author': 'Ubiguchi', 'author_id': 2562, 'author_profile': 'https://Stackoverflow.com/users/2562', 'pm_score': 5, 'selected': True, 'text': '<p>To ensure your WCF application can scale to the desired level I think you might need to tweak your thinking about the stats your services have to meet.</p>\n\n<p>You mention servicing "1000+ client users" but to gauge if your services can perform at that level you\'ll also need to have some estimated usage figures, which will help you calculate some simpler stats such as the number of requests per second your app needs to handle.</p>\n\n<p>Having just finished working on a WCF project we managed to get 400 requests per second on our test hardware, which combined with our expected usage pattern of each user making 300 requests a day indicated we could handle an average of 100,000 users a day (assuming a flat usage graph across the day). </p>\n\n<p>In addition, since it\'s fairly common to make the WCF service code stateless, it\'s pretty easy to scale out the actual WCF code by adding additional boxes, which means the overall performance of your system is much more likely to be limited by your business logic and persistence layer than it is by WCF.</p>\n'}, {'answer_id': 90564, 'author': 'MotoWilliams', 'author_id': 2730, 'author_profile': 'https://Stackoverflow.com/users/2730', 'pm_score': 2, 'selected': False, 'text': "<p>Probably the 4 biggest things you can start looking at first (besides just having good service code) are items related to:</p>\n\n<ul>\n<li><strong>Bindings</strong> - some binding and they protocols they run on are just faster than others, tcp is going to be faster than any of the http bindings</li>\n<li><strong>Instance Mode</strong> - this determines how your classes are allocated against the session callers</li>\n<li><strong>One &amp; Two Way Operations</strong> - if a response isn't needed back to the client, then do one-way</li>\n<li><strong>Throttling</strong> - Max Sessions / Concurant Calls and Instances</li>\n</ul>\n\n<p>They did design WCF to be secure by default so the defaults are very limiting.</p>\n"}]
['https://Stackoverflow.com/questions/43823', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/1078/']