Recently TriggerMesh, a cloud native integration platform provider, announced that their Cloud Native Integration Platform is now open source and available under the Apache Software License 2.0. It allows cloud operators and DevOps practitioners to freely deploy integrations as code.
The integration platform from the company aims to provide users with a solution similar to "infrastructure as code" (IaC) solutions such as Ansible, Chef, HashiCorp, and Puppet, which DevOps teams use to deploy infrastructure. It is built on top of Kubernetes and provides a declarative API, an Integration Language to quickly and programmatically connect data and services into event-driven applications.
Source: https://www.triggermesh.com/
Integration between systems using the platform is based upon event-driven architecture patterns. The platform can consume messages from various sources (e.g., AWS SQS, Google Storage, Azure Activity Logs), filtering and transforming them, combining processing capabilities with serverless functions, and connecting with message sinks (e.g., Elasticsearch, AWS S3, Apache Kafka). Furthermore, it can work with legacy enterprise services buses (ESBs) such as Mulesoft, Tibco, IBM MQ, and RabbitMQ to create workflows between applications or data sinks to other systems (e.g. Azure Data Lakes or Snowflake).
In a recent TriggerMesh blog post, co-founder Sebastien Goasguen, provides a few examples of what potential integration can be built using the integration platform:
For example, you can build a data pipeline to fill your data lake, storing all your Git commits or all your Salesforce events in an ElasticSearch cluster. You can grab all your logs from Azure and store them in Splunk after having filtered and annotated them. You can grab metrics from anywhere and store them in Datadog. You can run an AWS comprehend analysis on objects stored in Google Storage.
From a market perspective, the Triggermesh Cloud Native Integration platform is an integration Platform as a Service (iPaaS) offering comparable to Microsoft Logic Apps, Boomi, and Jitterbit. Additionally, the TriggerMesh integration platform provides connectors, a workflow language, and a hosting environment similar to those offerings. However, as TriggerMesh co-founder and CEO Mark Hinkle told InfoQ:
What makes TriggerMesh a revolutionary solution is that it is the industry's only open source cloud-native iPaaS (Integration Platform-as-a-Service) built on Kubernetes. We feel that the TriggerMesh solution provides an essential building block for building multi-cloud real-time data flows; our aim is to become the de facto integration platform for building event-driven applications on Kubernetes.
Also in a TriggerMesh press release, Graham Siener, vice-president of product for VMware Tanzu, said:
As event-driven systems become more popular, developers are realizing that integrating events across sources and environments is a big challenge. This is exacerbated by hybrid and multi-cloud topologies that lead to more disparate sources of all shapes. So when we looked at our options to provide Cloud Native Runtimes users with a single API for automating how events are consumed, regardless of the event source, Triggermesh was the clear partner. The integration with TriggerMesh makes it easy for Knative eventing resources to consume external events across all the clouds.
Lastly, the company provides free training for the platform, and more details are available on the FAQ page and documentation pages.
