| Title: |
Concurrency Patterns for SOA |
| Author: |
John Butler |
| Publication Date: |
26 April 2007 |
| Report Type: |
Journal |
| Report Class: |
Best Practice |
| Abstract: |
Large-scale service oriented architectures offer simultaneous access to critical data to hundreds, thousands, or in the case of the Internet, even millions of users. Managing concurrency in systems of this magnitude is a challenge to say the least. Fortunately, systems of this scale are nothing new and many of the problems that arise with such systems have already been solved using transaction managers. Service oriented architectures differ in that they tend to be much more highly distributed and loosely coupled and the resources managed therein often span organizational boundaries. These characteristics limit the ability of TP Monitors to share transaction contexts and so new solutions are called for. This article discusses concurrency issues and architectural patterns to handle them. |
| Backgrounder: |
Typically developers learn about programming concepts by building relatively simple stand-alone applications. While the algorithms they build often evolve to become very complex, developers are rarely exposed to situations involving multiple programs or processes trying to access the same resource, either hardware (e.g. memory, processor, or sensor) or software (e.g. software module instances or data) at the same time. What they soon come to realize is that in the business world 95% of the systems built have to deal with this reality and SOA is no different in this aspect. Our experience has shown that any mature SOA has to address these concerns.
Drivers
The issue of concurrency arises from the simple fact that multi-user programs compete for scarce resources particularly as the number of requests from those users begins to scale up. While we will talk about several types of concurrency in the article below, first and foremost is the need to effectively deal with concurrent access to data. After all, the whole point of business applications is to share accurate information about the business or organization so that operations run more smoothly. |
| Report Size: |
10 pages |
| Report Access Type: |
 | Silver/Gold (Premium) |
|
| Available for separate purchase |
Single copies of recent CBDI Journals may be purchased |
| Login |
|
Home