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.



Popular posts from this blog

Teiid Platform Sizing Guidelines and Limitations

Users/customers always ask us about the sizing of their Data Virtaulization infrastructure based on Teiid or the JDV product from Redhat. Typically this is very involved question and not a very easy one answer in plain terms. This is due to fact that it involves taking into consideration questions like:
What kind of sources that user is working with? Relational, file, CRM, NoSQL etc.How many sources they are trying to integrate? 10, 20, 100?What are the volumes of data they are working with? 10K, 100K, 1M+?What are the query latency times from the sources? How you are using Teiid to implement the data integration/virtualization solution. What kind of queries that user is executing? Even small federated results may take a lot of server side processing - especially if the plan needs tweaking.Is materializing being used?Is query written in optimal way?and so on..Each and every one of the question affects the performance profoundly, and if you got mixture of those then it become that much…

Teiid Runtimes Explained

If you have been following Teiid lately we have been going through a whole lot of renovations. Yes, renovations or reorganization or refactoring or whatever you want to call it. Basically, we are making Teiid more modular with fewer dependencies that can be used by however your use case dictates rather than use it as one monolith application deployed into WildFly JEE Application Server. There is nothing wrong in using Teiid as server model, but with the proliferation of container-based workloads and cloud-based architectures, the previous server-based model does not work or simply won't scale. So, we needed to think of alternatives, thus Teiid team introduced a couple different versions modular Teiid what we are calling as "Teiid Runtimes".

Note that in these modular Teiid runtimes, not all the features you were used to using in Teiid Server model may not be there but you will have extensions to add in those that are most appropriate for your domain. If you are looking …