Designing Systems for Application Concurrency


One of the amazing things about application development is how well applications tend to both behave and scale with only one concurrent user. Most developers are familiar with the wonderful feeling of checking in complex code at the end of an exhaustingly long release cycle and going home confident in the fact that everything works, and performs, to spec. Alas, that feeling can be instantly ripped away, transformed into excruciating pain, when the multitude of actual end users start hammering away at the system, and it becomes obvious that just a bit more testing of concurrent utilization might have been helpful. Unless your application will be used by only one user at a time, it simply can’t be designed and developed as though it will be.


Concurrency Control Service Broker Repeatable Read Timeout Period Snapshot Isolation 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Copyright information

© Adam Machanic, Hugo Kornelis, Lara Rubbelke 2007

Personalised recommendations