Visualize the following scenario: All enterprise content (wherever generated by whatever entity) goes into a single repository and users can receive different services (that they were receiving from different applications earlier, or are completely new services) from an integrated system with a standard front end. Service Oriented Architecture, Enterprise Application Integration, and Data Warehousing work to make this scenario a reality.
Data warehouses, unlike transactional databases, are designed to facilitate querying and analysis. They are separated from transactional databases so that the latter are not burdened with query/analysis processing requests. These kinds of requests tend to use the processing resources, slowing down transaction processing response times.
Enterprise Application Integration seeks to integrate the different applications to eliminate duplication of both content and processing operations.
This article explores how Service Oriented Architecture works.
The Service Oriented Architecture (SOA)
This style of architecture groups functionalities into specific service groups. The services are provided to manage...