Skip to main content

Teiid Spring Boot 1.5.0 Released

I am excited to announce that Teiid Spring Boot version 1.5.0 released today to the maven repository based on Teiid 14.0.0 release.

If you have not used Teiid Spring Boot before, it is built on top Teiid Core libraries with developer simplification in mind. It simplifies the deployment model to a single VDB and provides you with executable binary rather than Server like WildFly where you need to deploy your VDBs.

The release highlights are

* Cassandra Data Source support
* Materialization automation
* Spring Boot version to 2.2.6
* Keystore/Truststore simplifications that work across the system
* SOAP Data Source support
* FTP Database Support
* A Lot of changes to detect data sources based on their inclusion as dependencies and consistent naming schemes across both Teiid and Teiid Spring Boot.

For a full list see this

Take look at the various examples in Teiid Spring Boot and take it for test drive let me know if there are any issues or improvements you see.



Popular posts from this blog

Teiid Spring Boot 1.7.0 Released

Teiid Spring Boot version 1.7.0 to support Teiid 16.0 has been released. This release is mainly to support the Teiid's latest version.  In this release, the support for OpenAPI code generation based on VDB has been removed as there is no community interest and moreover it was at OpenAPI 2.0, and the industry has moved to 3.0 and beyond. There are no plans to further pursue this feature. VDB maven plugin was also removed, which was intended to be a replacement for the VDB importing feature was to be used when working on OpenShift, however, since it requires the Maven repository and does not completely represent the feature as defined on the WildFly based deployments this is also removed. You can still use the VDB import feature with Teiid Spring Boot, simply define the VDB with your "IMPORT DATABASE" statements and provide the additional files along with the main VDB file. During the start of the application, Teiid Spring Boot will load all the necessary DDL files for the

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 looki

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