Skip to main content

Data Integration for Java Developers - Introducing "Teiid Spring Boot"

Are you trying to integrate data from a REST web service with a data in your legacy RDBMS database?  How about data from Excel or CSV file,  JSON,  XML, MongoDB contents? As Java developers we know how to read the data from these sources and how to stitch data together, all it takes some boilerplate code right?

How about running some filters on that data, working with data type incompatibilities between data sources like converting a string type to decimal, doing aggregations like grouping the records by certain parameters and finally exposing it as REST service and you got 30 minutes do it?


If you have NOT heard about Teiid (t-ee-d) before, this software is exactly what it is designed to do. It has many more features, but let's focus on Data Integration feature. One of the basic features of Teiid is to provide ways to integrate data from multiple disparate sources where it knows how to work with data type incompatibilities and provides a relational data engine that can plan a very optimized query to fetch only the data that you are interested in and let you combine data with the power of SQL.  


If you have used Teiid before, you may have configured data sources in WildFly Server and designed Virtual Databases using Designer or Dynamic VDBs with DDL and deployed them into Teiid Server and used JDBC from your Java application to query it. 


Now, there is completely a "new" way to approach the problem with simplified options for Java developers. No more VDBs or Servers etc.

We are introducing a brand new sub-project called "Teiid Spring Boot" for Java developers which unleashes the same power and flexibility of Teiid's Data Integration and Virtualization features while harnessing the power of Spring Boot where using the conventions over configuration makes it developing an application much much more simple.


There are no lengthy APIs to learn if you are familiar with JPA and Spring Boot based programming, and SQL you already know most of it. The rest of the Teiid's Data Integration techniques that are defined using Java Annotations on the Entity you defined. For example, here are typical steps involved

  • Define the data source(s) and provide the configuration parameters such as connection URL, username, password as Spring requires. 
  • Write a JPA Entity (View) that you like to expose to your application
  • Decorate JPA Entity with additional Teiid specific Java Annotation and provide any SQL based integration logic as needed based on data source created.
  • Use Spring Data API query your Entity model you created.
If you are ready to take to this for spin take a look at this example where data from two different Postgres databases are being integrated and shown in the single Entity.

This is especially exciting new framework if you are developing Spring Boot based Microservices and need to integrate with your legacy RDBMS but at the same time not compromise on database per service. More on this later in future blogs.


I encourage take 15 minutes and take it for a spin.

Ramesh..


Comments

Popular posts from this blog

Tech Tip: Teiid SQL Language MAKEDEP Hint Explained

In this article I will explain what a MAKEDEP hint is, how and when, why it should be used in Teiid. What: MAKEDEP is query hint.  When a query hint is defined in the SQL query it influences the Teiid query planner to optimize the query in a way that is driven by the user. MAKEDEP means "make this as a dependent join". What is a Dependent Join? For example if we have query like: SELECT * FROM X INNER JOIN Y ON X.PK = Y.FK Where the data for X, and Y are coming from two different sources like Oracle and WebService in Teiid, so in relational algebra you can represent above query as Here the result tuples from node X and node Y are being simultaneously fetched by Teiid query engine, then it joins the both the results inside Teiid engine based on the specified X.PK = Y.PK condition and returns the filtered resulted to the user. simple.. Now, what if, if X table has 5 rows and Y table has 100K rows? In order to do the JOIN naively Teiid need sto read all the 5

Teiid 8.11 Beta1 and 8.10.1 Released

Teiid 8.11 Beta1 is now available from the  downloads  and maven.  Feature highlights since Alpha2 include: TEIID-3434 More caching control over ttls in the result set cache down to the schema/table level. TEIID-3412 MS Access support via the UCanAccess driver. The UCanAccess support is necessary for those running on Java 1.8 as the JDBC ODBC bridge has been removed from the JRE. The waiting continues on EAP 6.4 Alpha1 - it still should be available shortly and should be the platform target for Teiid 8.11 Beta2. Of course, let us know if you find any issues with these early releases.  There's still plenty of time to get fixes into the final release. Teiid 8.10.1 is also available.  It addresses 5 important issues discovered since 8.10 was released: [ TEIID-3409 ] - PostgreSQLExecutionFactory TranslatorProperty annotation in wrong place [ TEIID-3437 ] - Inconsistencies with row count handling [ TEIID-3438 ] - Null value returned from BlobImpl

Teiid 8.13.3 Released

Teiid 8.13.3 is now  available .  In total 8.13.3 addresses 10 issues since 8.13.2: [ TEIID-4028 ] - adding salesforce-34 resource adapter does not work through the cli [ TEIID-4066 ] - Odata translator ClassNotFoundException: com.sun.ws.rs.ext.RuntimeDelegateImpl [ TEIID-4070 ] - Issues with resource adapters with api modules in wildfly [ TEIID-4089 ] - Teiid JDBC driver does not reset the update count when calling getMoreResults(int) [ TEIID-4093 ] - OData authentication fails with NPE when gss-pattern related properties are included in VDB [ TEIID-4096 ] - AssertionError with independent side of a dependent join that has an ordered limit [ TEIID-3050 ] - allow for more incremental insert with iterator [ TEIID-4075 ] - Netezza translator to support common table expressions [ TEIID-4098 ] - Always preserve columns order in google spreadsheets models [ TEIID-4046 ] - OData - $skip is beeing ignor