Service Oriented Architecture and Mass Data Movement
The Service Consumer and Service Provider leverage the data tier constructs of the Staging Area and the Intermediate Area to exchange the bulk of the data needed to fulfill the business call interaction. In addition, they use the Integration Layer components such as the ESB to help mediate, monitor, and manage the call notifications and the call prioritizations.
In conclusion, this pattern when applied to certain use cases allows the enterprise to embark on SOA style implementations where by interactions with specialized Service Providers require trading all of the relevant business or application data during the execution of the call due to the limitations of the hosting platform of the Service Provider. In these circumstances, the use of the Staging Area and Intermediate Area constructs enable using more optimized interactions with "niche" service providers that offer computation-oriented functionality (process bound) or federated information gathering type functionality. Thus, application of this architecture model allows interactions with these type of "utility" service providers to still utilize SOA principles of loose coupling without sacrificing the core strengths of these specialized Service Providers.
About the Author
Surekha Durvasula is an enterprise architect who has had 10 years experience in designing and architecting a variety of enterprise applications in the financial services sector and the retail industry vertical. Most of her work has been in the area of distributed N-tiered architecture, including J2EE component architecture. Her more recent focus has been on Service Oriented Architecture and Business Process Management. Her efforts as an Enterprise Architect involve not only architecting new applications and business services but also in leveraging the principles of SOA to extend the life of existing Enterprise Information Systems.
You can contact Surekha at the following email address: email@example.com
Page 2 of 2