Designing Systems for Application Concurrency
It is hardly surprising how well applications tend to both behave and scale when they have only one concurrent user. Many 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 according to specification. 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.
KeywordsResource Pool Service Broker Repeatable Read Resource Governor Snapshot Isolation
Unable to display preview. Download preview PDF.