Skip to main content

Quickstart example with Dockerized Teiid

Container based deployments for any services seemed to be picking up stream in every IT department, so to keep up with pace, Teiid released its Docker image for its 8.10.Final version.  

In this article, I will showcase same quick start example from Teiid, but using the docker based images. if you interested in that please read the complete article at




  1. Are there plans to keep the docker images current?

  2. Yes. 9.x images should be available shortly.

  3. I updated 9.1 Docker image at will need to work on build

  4. I'm hoping this is kept up to date in line with releases...

  5. What the example? Is it not working?

    1. Sorry, I meant that I hope the docker images are kept up to date with TeiiD releases.

  6. Symantec Blue Coat Web Filter had your blog categorized as spam and I couldn't get to it from work. I submitted a review request and they opened it up. Just thought you should know.


Post a Comment

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 …