There are two main advantages. First, when running in AWS Lambda you run your functions within the AWS function runtime. You do not control that runtime, it has pros and cons but with TriggerMesh you can define exactly the runtime that you want to run in. Some might say that it goes against the _serverless_ philosophy but it also means more control. The second is that AWS lambda functions are triggered on AWS event sources alone. AWS does offer a large set of event sources but you are limited to their services. If you want to trigger a function based on a Google cloud service or an Azure cloud service like Azure Storage queues you cannot do it. In TriggerMesh we aim to give you a large set of triggers from multiple cloud providers and also from on-prem applications. This will ultimately give you a more portable serverless workload.
Find answers to common questions or reach out to our support
Connect services together to automate workflows and accelerate the flow of information across your organization.