Posted by: ITKE
Administration, interoperability and integration, Red Hat
A tidbit from an upcoming SearchEnterpriseLinux.com Q&A with Red Hat vice president of enterprise applications Tim Yeaton:
What was behind the data management-related Meta Matrix Data acquisition?
Yeaton: The way I like to describe it is ‘federated data access and integration.’ Imagine having a middleware layer mediating between your core applications and other applications, like EAI and ESBs. What Meta Matrix adds is the ability to delegate with multiple heterogeneous data sources in an abstract way. The application goes to the Meta Matrix layer, or the data federation layer, and it can access any data source it is authorized to regardless of type or location. What this is good for is applications that have to access multiple heterogeneous data sources like portals, business intelligence, enterprise reporting and dashboards; where the application is accessing 20-30 data sources. Some are relational and some are not, but the user wants a unified view of that application without having to hand code access to those data sources.
Red Hat is really making a push to be the single point provider for much of the software stack running in today’s enterprises. They’re covering middleware with JBoss, file and print sharing with that stable of Samba developers who came over after the Microsoft-Novell partnership fallout, and now Meta Matrix for its data management needs. They also have a bunch of ID management expertise left over from the Netscape days, too. No wonder Yeaton was summarily unfazed by my questions about Oracle Linux and Microsoft moving in on their turf.