This post was written by a guest contributor, Chris Baumbauer, engineer at TriggerMesh.
As part of our continuing commitment to open standards and supporting a broad and varied ecosystem, we’re pleased to announce that TriggerMesh has extended its Cloud Native Integration Platform to support on-premises Oracle, Oracle Cloud Infrastructure (OCI), and Oracle Container Engine for Kubernetes (OKE).TriggerMesh, which is available on the Oracle Cloud Marketplace, enables real-time integration with Oracle Database and cloud services, so Oracle customers can build event-driven applications out of any on-premises application and any cloud service.
Cloud computing frees developers to focus on writing business logic and leave the undifferentiated software to any number of cloud providers. This software includes a general-purpose cloud, like OCI, a dedicated SaaS cloud-like Elastic, Datadog, or NetSuite, or an on-premises cloud running OKE. With serverless, the cloud infrastructure also becomes increasingly touchless and granular.
Most enterprises now have a heterogeneous mix of services running on the “best” cloud for each workload. This mix can present a challenge when you need to connect the insights from one service, such as CRM, with the users of other systems, such as finance or ERP. As cloud services become more discreet and more numerous, the need for agile integration grows exponentially.To meet this need, developers are increasingly embracing what we at TriggerMesh call the SMOKE stack: Serviceful, Multicloud, Open source, Kubernetes, and Event-driven. We cover this stack in detail in our technical brief.
The TriggerMesh Cloud Native Integration Platform provides developers with a modern, event-driven approach to multicloud integration. Let’s look at how this next-gen integration approach differs from legacy message-based integration tools with which you might be familiar.
Legacy integration tools, such as Dell Boomi and Mulesoft, tightly couple the payload with the integration message. This process includes writing, installing, and maintaining integration libraries everywhere. Maybe not a big deal for one or even a few relatively static integrations. As the number of cloud services skyrockets, this integration approach fails.
TriggerMesh cloud native integration, which is based on event-driven architecture (EDA), surpasses simple message-oriented integration. Events differ from messages in that events are simply a notification that a change in state occurred, such as for sale or sold, new customer, and new billing information.
With TriggerMesh, the applications publishing events or event sources don’t need to know anything about their subscribers or targets. In this modern model, event targets decide which event sources they’re interested in. This selectivity enables a constant state of awareness so that producers can stream data about various types of events or topics in real time to all potential consumers. Because it’s cloud native, all this power comes in a portable, agile, scale-to-zero package.
The TriggerMesh and Oracle partnership opens enormous opportunities to take control of your architectural strategy. Now, you don’t need lift and shift to benefit from the cloud. You can progressively modernize on-premises applications with event-driven integration to any other system or service, no matter where it’s running.
TriggerMesh offers two consumption models to support enterprises’ varied use cases and skill levels. For less complex use cases, and for less technical users, use our low-code UI to create application flows, which we call bridges. For teams more comfortable with DevOps approaches, TriggerMesh offers a powerful declarative API to create integrations-as-code. Customers often use the TriggerMesh API with their existing continuous integration-continuous deployment (CI/CD) pipeline for a fully automated GitOps approach to cloud native integration.
To demonstrate the unique capabilities of TriggerMesh with Oracle Cloud, we recently performed a proof of concept that integrated OCI metric events in real time with Datadog. So, the customer can maintain a single pane view of their application performance.
View the recorded webinar from May 12th “Multicloud integration made easy: Real-time cloud integration for Oracle customers.” with TriggerMesh Engineer Chris Baumbauer. Chris demonstrates how developers, DevOps, and architects can rapidly create an integration between Oracle Cloud and Datadog. To highlight the versatility of TriggerMesh multicloud event integration, we also demo adding AWS CloudWatch Metrics as a source.
To build your own integration, see the following resources: