Skip to main content

Welcoming the Komodo dragon

Komodo dragon
noun Ko·mo·do dragon \kə-ˈmō-dō-\
:  an Indonesian monitor lizard (Varanus komodoensis) that is the largest of all known lizards and may attain a length of 10 feet (3 meters) 

(See http://www.merriam-webster.com/dictionary/komodo%20dragon

For the better part of 13 years, the primary relational modelling support behind the Teiid runtime VDB has been backed by a handful of Eclipse's EMF E-core models. Just the fact of using the "E-core" sends shivers down my spine, but it's served it's purpose for over a decade. Unfortunately, as we move forward with Teiid runtime improvements, it's become apparent that sticking with EMF (and maybe Eclipse) has become a roadblock to implementing new and more robust modelling concepts.

So, over the past year, the Teiid Designer team has been gearing up to remove the burdens of that Eclipse framework and embracing the simplicity of traditional DB terminology. In particular DDL. This initiative has been code-named Komodo as a reference to both it's Teiid (Teiidae) lineage and to the awesome power of this largest of all lizards.
In a nutshell, we're utilizing a design-time Modeshape/JCR repository for managing and persisting our design-time metadata (VDB, DDL, etc...) which allows consistent import/export of runtime metadata.

Here's a link to our on-going Komodo project plan:
https://developer.jboss.org/wiki/TeiidDesigner-KomodoReleaseDevelopmentPlan

Also check out a recent Komodo status presentation dated Feb 15, 2015.  Comments and suggestions are most welcome!!

So expect some buzz on this channel in the coming months. We're bringing the Komodo Engine on-line as we speak and will hopefully have initial UI prototypes to play with in a few weeks.

Barry LaFond
Teiid Designer Project


Comments

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 …