This article originally appeared on the BeyeNETWORK
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Building on Part I of this series, this article will discuss how DW2.0 forms a foundation for service-oriented architectures.
There actually are many ways that DW2.0 sets the stage for a service-oriented architecture (SOA). The first way that SOA is accommodated is in that DW2.0 contains the data that SOA needs. In DW2.0, that data is easy to find. DW2.0 compartmentalizes data so that it is very clear as to where any given unit of data is to be found. Because DW2.0 brings together many different types of data under one “roof,” there is an order to the data that service-oriented architectures require.
The second way that DW2.0 sets the stage for service-oriented architectures is in terms of integrating data. DW2.0 doesn’t just contain a lot of data. DW2.0 mandates that data be integrated as it is brought into DW2.0. This means that data is immediately useful. If data is measured in dollars, the dollar refers to the same dollar – Canadian dollars, U.S. dollars or Australian dollars – not a mixture of the three. If data is encoded by gender, it is guaranteed that all males are “M”, not “males”, “X”, or “1.” If data is defined as being CUSTOMER, then it is just that, not prospects or former customers. In a word, by having the data integrated into DW2.0, the information is as meaningful and useful to SOA as it is easily accessible.
Not only is information integrated in DW2.0, but it also is immediately available. The performance needs of DW2.0 are mitigated. Data from the interactive sector of DW2.0 is available in an online manner. It is the norm for data to be accessible in an up-to-the-second basis in DW2.0. Thus, if SOA requires up-to-the-second, online availability of data, then DW2.0 can supply that level of performance.
DW2.0 provides a simple technological interface. Since DW2.0 requires that data be gathered together and organized by data type, when SOA needs data, it only has to deal with a single technological interface. Were it not for DW2.0, SOA would have to go into many different types of technology in order to satisfy the informational needs served on the Web.
DW2.0 makes both structured and unstructured data available to SOA. Without the infrastructure that is built for DW2.0, accessing unstructured data is very difficult, if not impossible, to accomplish. DW2.0 also provides the basis for making the linkage between the structured and unstructured environments.
DW2.0 requires that metadata be present and tightly constructed. By having a solid infrastructure of metadata, DW2.0 allows data to be found that otherwise would not be obvious or available at all.
DW2.0 separates data by probability of access. This means that popular, regularly accessed data is not dragged down by older, less popular data. This segmentation of data by probability of access enables DW2.0 to provide the ultimate in performance for service-oriented architectures.
DW2.0 provides granular data. The granular data means that all sorts of informational requests can be handled. Without granular data, there is limited functionality that can be accommodated. However, with granular data, DW2.0 can serve practically any request for information that can be generated by service-oriented architectures.
These are just a few of the ways that DW2.0 sets the stage for service-oriented architectures. Stated differently, without DW2.0, a service-oriented architecture would have a hard time finding and processing data. DW2.0 is the perfect background architecture to make service-oriented architectures successful.
The complete definition of DW2.0 can be found on http://www.inmoncif.com/ under the section on DW2.0.