TriggerMesh this week at the KubeCon + CloudNativeCon North America conference revealed that it is making the Kubernetes-based TriggerMesh integration platform available under an open source Apache 2.0 software license.
Mark Hinkle, CEO of TriggerMesh, said that as other open source initiatives have shown, the number of organizations likely to adopt TriggerMesh Integration Platform increases when developers within organizations can download it without requiring the approval of a purchasing organization.
The TriggerMesh platform provides access to a cloud bus to facilitate the orchestration of application flows and consumption of events from any data center application or cloud source. It is designed to trigger serverless functions using a declarative application programming interface (API) and a set of tools to define event flows and functions.
Designed to foster a shift towards an integration as code approach enabling event-driven workflows, TriggerMesh also promotes the adoption of a TriggerMesh Integration Language (TIL) that simplifies the creation and maintenance of integrations in Kubernetes environments by eliminating the need to rely on YAML files. Instead, TIL provides access to a higher-level declarative language that provides an abstraction of Kubernetes objects using the HashiCorp Configuration Language (HCL) used to provide infrastructure as code (IaC).
The platform itself is built on top of open source Knative middleware running on Kubernetes clusters that has been extended by TriggerMesh to add support for proprietary serverless computing frameworks such as Lambda from Amazon Web Services (AWS).
Most recently, TriggerMesh received an undisclosed amount of investment from Cisco after raising additional funding of $ 5 million earlier this year. The company is now focused on providing enterprise support alongside additional extensions to the core TriggerMesh integration platform.
This platform is designed to enable organizations to move to the event-driven IT architectures that are at the heart of many business digital transformation initiatives. As data is increasingly processed and analyzed at the edge, there is a need to update back-end systems in near real time rather than continuing to rely on batch updates that may only take place. once a day. End users now expect data accessed through a digital business process to be as current as possible.
Event architectures, of course, are not a new idea, but with the rise of serverless computing infrastructures, they are becoming much easier to invoke. They are often invoked through a cloud service without an in-house IT operations team required to deploy and maintain a middleware platform. None of this means that traditional batch-oriented applications are going to die out anytime soon, but it does mean that the overall IT environment will become more diverse as more and more event platforms are deployed.
In the meantime, IT teams will need to decide whether a new approach to integration is needed as part of this transition rather than waiting for legacy integration platform vendors to better support modern cloud native applications. .