Tuesday, May 9, 2017

Teiid 10 Planning

As we get closer to staring on Teiid 10.x, we want to elicit as much community feedback on our initiatives as possible.  Some of the major themes are:
  • Refining our messaging around and our usage of WildFly TEIID-4895
  • Removal of the XML document model logic TEIID-4894 and other deprecated features
  • Spring Boot TEIID-4863 and eventually vert.x support
  • More documentation and demos around microservices
  • General project updates including 
    • more build automation
    • possibly do away with pre-release names (e.g. Beta1) and instead promote specific micro releases
    • Relicense under a more permissive license TEIID-4474
Of course there's a lot more already in the 10.0 and 10.x release buckets as well.  Please provide whatever feedback you can - especially on WildFly usage.  Also have a look at all of your relevant issues and comment or vote on any that need more immediate inclusion.

Beyond the core project we are in the initial stages of working towards an OpenShift ready data integration suite including:
If you have any desire to coordinate on these additional efforts, please let us know so that we can loop you in once the appropriate git and other resources are in place.



  1. For Teiid 10, can more usability items be prioritized. For example, the difficult to use developer tooling and the requirement to use odjbc postgresql driver for .NET connectivity. I feel those will do more to grow the Teiid community than just adding additional connectivity.

    1. Adil,

      Does Npgsql [1] help with .NET access to Teiid? May be we can fix any incompatibilities with that.


      [1] http://www.npgsql.org/

    2. Thank you for your response. I haven't looked into that library myself when I evaluated Red Hat JBoss Data Virtualization. Having Teiid/Red Hat JBoss Data Virtualization have that as the supported and preferred way of connecting from the .NET platform would instill a lot of confidence. I will look into it when I get some free time.