Blog: William McKnight« Best, worst... and craziest uses of RFID | Main | When Not to Use Enterprise Information Integration » When to use Enterprise Information Integration (EII)This blog entry is co-authored by William McKnight and Mike Ferguson (link) and is being cross-posted on our blogs. This is the first in a series of entries on Enterprise Information Integration (EII). EII is gaining traction for enabling data integration without the need for the physical instantiation of the integration. In other words, EII adds integrated reporting capabilities while minimizing impact on existing systems. We have been selectively adding EII to our data warehouse architectures. Today, we’ll look at those situations when EII makes sense for data integration requirements. EII is changing and some of the disadvantages and restrictions will lessen over time but it’s a chicken-and-egg situation. More end clients will need to incorporate small adaptations of EII in their decisioning environment to spur the growth. There may be opportunities and TCO propositions to federate your data acquisition requirements now using EII. Small sized, relatively smaller transformations, unstructured and interactive situations provide those opportunities. |
Comments
Great summary, guys. I think your analysis is right on the money. The one situation I might add is when you are trying to make your data available to a new SOA project. Perhaps this is where you might see some departmental implementations.
Posted by: Tim Matthews | January 5, 2007 1:05 PM
Thanks for posting this summary online, great help. Demand of EII is growing vertically. Please keep posting such articles, it will be very helpful for us.
Regards.
Posted by: Nilay Parikh | January 20, 2008 11:24 AM