The Role of an EDW in an SOA
•Télécharger en tant que PPT, PDF•
0 j'aime•802 vues
For more information, visit Teradata.com
![What Is SOA? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Recommandé
Contenu connexe
En vedette
En vedette (8)
Plus de Teradata
Plus de Teradata (19)
Dernier
Dernier (20)
The Role of an EDW in an SOA
- 1. The Role of an Enterprise Data Warehouse in a Service Oriented Architecture David Brand Senior Solution Architect Teradata Corporation
Notes de l'éditeur
- There are many parallels between data mart consolidation and SOA. One might say the Java and .Net architects are “normalizing” their code, much the same way we normalize a database design. With SOA we have inconsistent data definitions and processing for the same data elements in multiple applications. We also have considerable amounts of duplicate logic in the applications since they all need to handle such things as currency conversions, price discount schedules, etc. These duplicate independent modules also demand a minimum set of middleware and hardware infrastructure, gobbling up the IT budget on duplicate processes. Last, these independent processes require duplicate labor for maintenance, research, and enhancements. Since each application is independent, a simple business required change can take days or weeks of research to validate implications, get the right modules selected for enhancement, and then upgrade and test multiple application components. This sounds a lot like data marts where duplicate data demands excessive infrastructure, hardware, labor, and maintenance. So, like DMC, SOA is a long term objective to consolidate many applications into one integrated set of Web services modules. As time progresses, the TCO of the applications decreases and maintenance becomes both cheaper and easier. Like Data Mart consolidation, the value of the composite application increases as more and more applications are decomposed and combined. Just like adding subject areas to the data warehouse, adding a collection of SOA modules from a new application to the baseline SOA collection increases the value of the entire collection. It provides new business process capabilities by allowing old processes to integrate and interact with new ones. So, like blending “customer” and “product” and “sales” data, blending the “order entry” application with “sales automation” and “marketing automation” produces new views of the business, new capabilities.