I am really proud of the work the TriggerMesh engineering team has put into our latest open source release, which dropped last week. This release expands Azure and Google Cloud Sources and adds key features to accelerate application modernization.
There are really dual motivations for the features in this release. On one hand, the additional Azure and Google Cloud Sources reflect our commitment to simplify multi-cloud application and data integration, which is a universal enterprise need. On the other hand, our work with companies with significant legacy systems like IBM MQ, mainframes, and proprietary iPaaS, informs this release’s features to accelerate application modernization.
To help architects and developers consume messages from multiple clouds, TriggerMesh now supports all the following Azure and Google Cloud Event Sources out of the box:
Google Cloud Sources:
Our ever-growing catalog of supported event sources for AWS, Azure, Google Cloud, SaaS tools like Salesforce, and streaming tools like Apache Kafka helps multi-cloud enterprises with a variety of use cases, such as building a security notification system across clouds to improve cloud governance.
A complete list of our 50+ Event Sources, Targets, and Connectors can be found here.
We have been working with several customers with legacy iPaaS platforms that they want to replace with open source infrastructure. The motivation is to reduce cost and avoid paying exorbitant license fees for proprietary solutions. They are looking for tools to accelerate the proprietary iPaaS take out.
To this end, this release adds IBM MQ as an open source Event Source and Event Target. This helps developers modernize legacy MQ applications and build cloud-native applications that are containerized and run in Kubernetes. For example, an enterprise can use TriggerMesh open source to quickly expose a REST API in front of a legacy mainframe system of record.
In tandem with the IBM MQ support, this release also includes two data Transformations to automate and scale the handling of XML data into cloud-native applications. The new XSLT Transformation and XML to JSON Transformation equip developers with out of the box XML transformation logic. Additional transformations will be coming in future releases to support even more legacy iPaaS migration use cases.
Finally, this release includes a synchronizing mechanism, which provides an API that uses a correlation id to wait for specific events answering to a request. Synchronizer can be used in conjunction with the IBM MQ Source and Target to build a synchronous API from an asynchronous event flow.
In summary, for enterprises looking to migrate from legacy iPaaS and modernize apps, TriggerMesh runs data transformations without refactoring scripts and connects to systems like MQ without proprietary connectors.