IT-Analysis.com
IT-Analysis.com Logo
Technology Data Management
Enterprise SME Business Issues Technology Services Channels
Module Header
Philip HowardBloor IM Blog
Philip Howard
8th February - Bribery
Nigel StanleyBloor Security Blog
Nigel Stanley
8th February - Conficker grounds police checks
David NorfolkThe Norfolk Punt
David Norfolk
3rd February - What's wrong with "security"
Laurie McCabeLaurie McCabe
Laurie McCabe
2nd February - What is Total Cost of Ownership, and Why Should You Care?
Philip HowardBloor IM Blog
Philip Howard
2nd February - Calpont finally comes to market
Module Header
Q. What features do you want to see on this site?
 
Analysis
A new approach to data integration
Philip Howard By: Philip Howard, Research Director - Data Management, Bloor Research
Published: 21st May 2008
Copyright Bloor Research © 2008
Logo for Bloor Research

Basically, all ETL (extract, transform and load) and data integration products work in the same way. Some may be code generating and some may be black boxes, some support or recommend ELT rather than ETL but they all have essentially similar architectures. In particular, they have all been designed for developers even though some of the major vendors like IBM, Business Objects and Informatica have been adding more business-oriented capabilities. However—and this is the point—they have been adding on such facilities.

However, expressor software has just announced its new product, which takes a fundamentally different approach to ETL. In a nutshell, whereas IBM (for example) offers a Business Glossary as an add-on to DataStage, expressor has its equivalent at the heart of its offering, around which the whole product has been built. However, there is more to it than that.

Specifically, expressor is semantically-aware. That is to say, it knows that customer# is the same thing as customer_no, which is the same as customer ID and so on. What that means in practice is two things: first, it means that the environment is much easier for business analysts to use in collaboration with developers, because it is using common terminology and, secondly, it means that mappings between sources and targets that have these equivalents can be automated and do not need to be specified.

Now, you might assume that you have to define these semantic equivalents and, indeed, in specialised circumstances you may need to. But the product, which will ship in June, will come with, to quote expressor, "hundreds of thousands" of built-in name correlations, pertaining to a range of different vertical markets. So, if you have to define your own equivalences they should be few and far between.

Of course, this doesn't mean that all transformations are automated but it does mean that a lot of the initial legwork is done for you, thereby significantly reducing the effort and time involved in defining data integration processes. Moreover, reuse is an automatic consequence of the semantic approach adopted by expressor and this also applies to business and transformation rules since these have the semantic basis.

In other respects, expressor is not too different from other data integration offerings, though it is surprisingly complete (see www.expressor-software.com) for a first general release, with version control, team development capabilities, project management, the usual flow design graphical interface, performance metrics, role-based security and so on. The expressor parallel processing engine runs under Windows, Linux, UNIX and on IBM mainframes with relevant tools being Windows or web-based. Project-based licenses are available and prices start at $20,000.

It is too early to predict how disruptive this will be but that is clearly the intention: to offer an innovative and appealing alternative to traditional approaches—I will watch and await developments with interest.

Reader Comments

Sorry, we are no longer accepting comments on this item. We suggest trying to contact the author directly.

23rd May 2008: 'Phil Bailey' said:

At last, ETL is getting 'smarter'. I wonder how long it will be before we are able to specify Requirements in English, and using NLP, we can identify potential sources from the metadata, and offer a heavily automated DW build-out, based on actual user/developer requirements - but importantly, traceable for ROI purposes.

Reply to Phil Bailey?

29th May 2008: 'Semyon Axelrod' said:

Finally (data) integration tool vendors see the light!
I agree completely.
Incorporating business processes (BPs) into the integration model (IM) and actually using BPs to drive a well-engineered IM as oppose to the prevailing bottom up “big ball of mud” type IM will provide huge savings to all the clients that can use it properly.
Some assembly and extra work would be required but the savings, especially long term and at the enterprise level should be able to justify this approach many times around.
If interested in learning about the logic behind this opinion, please see the article
“MDM is not enough”
www.dmreview.com/specialreports/2008_69/10000964-1.html

Reply to Semyon Axelrod?

11th July 2008: 'John O'Gorman' said:

It's a good first step, and I soon hope to have an offering that will not only tell that "...customer# is the same thing as customer_no, which is the same as customer ID..." but that the value stored as "customer# 1234" is the same organization as the value stored as "customer_no ABC67d7", which is the same organization as "supplier-ID N-899".

Reply to John O'Gorman?

Advertisement



Published by: IT Analysis Communications Ltd.
T: +44 (0)190 888 0760 | F: +44 (0)190 888 0761
Email: