Today, the entire TriggerMesh team is super excited to announce that our Cloud Native Integration Platform is now open source and available on GitHub. Only a small part of the team can make it to KubeCon due to travel restrictions but do stop by our booth (SU3) if you are there and even virtually where the rest of the team will be. We are looking forward to sharing our excitement and explaining to you why we think this is a game changer for application modernization and building event-driven applications.
Back at KubeCon NA 2020, I gave a virtual talk about “serverless vs serviceful”. This is what has inspired us since the beginning of TriggerMesh and me personally ever since I created Kubeless back in late 2016. Developers are modernizing their applications by taking advantage of cloud services wherever they are and from whoever the provider is. In addition, this modernization takes advantage of function-based offerings known as Function as a Service (FaaS) that auto-scale and provide a finer billing mechanism. That’s why we think that serverless should actually be called serviceful. And it’s also why we think that by focusing too much on functions, we often lose the fact that serverless offerings like AWS lambda are actually about events: ingesting, storing, emitting and processing events.
But what do you do with Events and Cloud services? Turns out going serviceful is about integrating services together. Whether it is an on-premises application or a Cloud service, whether it is containerized or not, whether it is called serverless or not. You are building applications that leverage many systems. The biggest challenge one faces when doing this integration is to avoid building a “bowl of spaghetti”, which might be delicious but would be unmaintainable. That’s why we have developed the TriggerMesh Cloud Native Integration Platform. Starting from a focus on serverless and functions, we quickly identified that the real benefit of serverless, and its biggest challenge, was one of integrating applications and services in the Cloud era.
Our Platform gives every user a set of APIs that can be used to define beginning and end of an integration or, as we call them, sources and targets. To make that integration work, our APIs also offer event transformation, event routing components, and a FaaS offering. These APIs— defined using the OpenAPI spec and implemented with Kubernetes—help to clearly declare the integration and avoid the unmaintainable spaghetti bowl. The reason we are announcing this at KubeCon is that of course we built it on top of Kubernetes. From an engineering perspective, TriggerMesh is a Kubernetes controller with all our APIs defined as Custom Resource Definitions. Which means that all Kubernetes users will be extremely familiar with the platform—Prometheus for monitoring, Fluentd for logging, RBAC, Quota, and GitOps. Hence why we call our platform “Cloud Native”.
Released today in our platform with an Apache license V2 are sources for most AWS services like SQS, S3 and Kinesis, sources for Google like Cloud Storage, Pub/Sub and Cloud Audit Logs, and to cover all three main clouds we are also releasing sources for Azure such as Azure Blob Storage and Azure Audit logs. All these sources together means that TriggerMesh provides you with the capability of Google EventArc and AWS EventBridge combined and on-premises. In addition to the sources and totally new in this release is the availability of so-called Targets like AWS SQS, Google Storage, Google Sheets, and also ElasticSearch and Splunk. The full list is available in our documentation
With this powerful open source platform you can quickly accomplish previously difficult cross-cloud workflows. 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. You can sync your IBM-MQ and your AWS SQS as you are developing new products in the Cloud, you can stream DB2 changes to the Cloud to build a read-only Cloud replica. You can manage your Kafka connectors whether you use AWS MSK or Confluent Cloud, no need for a Kafka connect cluster anymore and welcome to a GitOps workflow to manage how your produce and consume messages into Kafka. Finally you guessed it you can build any event-driven application and define it with our Kubernetes-backed declarative API. And with this open source announcement, we can’t wait to see what you build using TriggerMesh!
As you can tell, we are stoked, pumped, excited and we think you will be too. We are bringing the Kubernetes experience to application integration, simplifying maintenance and management of integrations, helping you bridge your on-premises application to Cloud service and helping you do things faster by being event-driven.