Amazon EventBridge vs TriggerMesh
Let's compare the two feature-by-feature to enable you to make informed decisions on which platform aligns best with your specific needs.
Google Cloud connectors
Managed by the vendor
Run it anywhere yourself
Community support channels
Consuming events from within Amazon EKS
EKS is Amazon’s managed Kubernetes service. There are times when platform teams will want to run many of their workloads on EKS. But if you want to ingest AWS events (or others) into EKS to trigger workloads there, there is no immediate way to do this with EventBridge, particularly if EKS is running in a VPC and can’t expose an API endpoint for EventBridge to call into as an API destination. There are other workarounds though such as using a Lambda function as a relay, or going through SQS or Step Functions.
TriggerMesh can run natively on EKS from where it can pull events into the cluster from external sources or AWS services and easily trigger workloads on the cluster. Granted in some cases TriggerMesh needs an intermediary SQS queue to pass the notifications through, but you’re still avoiding adding EventBridge into the mix.
Creating a cloud-agnostic serverless platform
If you are heavily invested in the AWS ecosystem, and want a hosted solution that provides tight integrations with AWS services, EventBridge could be the preferred choice.
If you value multicloud portability, a Kubernetes-native workflow, and open-source, then TriggerMesh is worth taking a look at. By choosing to create a serverless integration platform on Kubernetes, you can benefit from being able to port your platform, and the applications that run on it, across any managed or self-hosted Kubernetes distribution.
What is TriggerMesh’s positioning with respect to Amazon EventBridge?
TriggerMesh is an open-source, multicloud alternative to Amazon EventBridge.
Is it possible to use TriggerMesh in combination with Amazon EventBridge?
Can EventBridge be used to trigger workloads that run in EKS or other Kubernetes clusters?
The answer is it depends. On its own, EventBridge cannot push events into an EKS cluster if the latter is running in a VPC. There are alternative ways to address this by using a relay Lambda function, or an intermediary SQS queue or Amazon Step Functions. Alternatively, TriggerMesh can pull events from AWS services like S3 and SQS into EKS (rather than have the events pushed into the cluster), and can transform, filter and route the events to trigger containerized workloads running on EKS.