Data integration between multiple disparate sources is now as simple as writing SQL code in your application as if all your schema (tables, views and procedures) from different databases are co-located in a single data source.
No, I am not talking horizontal partitioning of your data that have same schema defined in all the databases that some other tools support. You can have segments of data to your liking or the way they were given to you. That not all, you can even add text files to this mix and use them as another source that is participating in data integration. All this is doable with Teiid.
All you have to do is to define the "data source(s)" you would like to integrate in a Teiid configuration file and configure Teiid as your JDBC data source in your application and start writing your application, which may be a simple JDBC or Hibernate application.
Sounds simple huh? Thanks to a new feature called "Connector Supplied Metadata", which is being introduced in the Teiid 6.2 release. This feature is so powerful that using it you can write a single EJB that reads or writes data to/from multiple sources, or you can write Hibernate application with single "Session Factory" that has domain objects from multiple different sources, where you can write Hibernate HQL query that joins two tables from different sources.
So What? Teiid had this capability all along!
Yes, you are right. There is nothing new in terms of additional capabilities of Teiid, it always supported data integration as its core capability. What is new is how it does it, and how flexible it is, and how fast you get from problem to the solution. Prior to Teiid 6.2 release in order to integrate two or more sources in Teiid the following steps must have to be taken.
Step 1: Using Teiid Designer, you need to import and create Source models
Step 2: Using the Teiid Designer, you need to create a VDB and add model files to VDB and configure the "Connectors" for the sources.
Step 3: Deploy into Teiid runtime.
Now, contrast the above scenario to below
as you can see the complete "modeling" step and building a VDB is eliminated (Step 1&2 from above) and metadata that is required for data integration is imported dynamically at runtime and working models are built automatically using "Connector Supplied Metadata" feature. However, user still needs to supply a configuration file where they can specify information about their sources! This configuration file called "Dynamic VDB". And you are required to deploy this configuration file into Teiid runtime engine.
This model does have its pros and cons, and may not suit all the data integration needs.
- Metadata about your source imported dynamically at runtime, you have an option to cache after the first import.
- No static model of your metadata, so it can keep changing as you change the source structure.
- No Teiid Designer tool to use, cutting down on time and learning curve with Designer.
- No VDB, i.e no custom artifacts to define your metadata, just define a simple XML file with your favourite editor.
- Possible to write dynamic discovery of sources and integrate them on the fly.
- You can not define virtual tables, procedures composing of multiple sources.
- You can not define a single view of your data.
- Many enterprise features may not be available.
- Currently only JBDC and Text based sources are supported, but more coming soon.
So, next time you think about combining data from your Excel sheet with your Oracle data, do not custom code the integration layer, use Teiid instead. Give it a try! and let us know what you think. Thank you for reading.
You can check out a quick example here.