Pros and cons using AWS EventBridge as webhook receiver

[Mads-Storebuddy]

Hi All

We are about to implement the use of webhooks into our service and we would like to have some inputs regarding AWS EventBridge vs. regular "self-build-managed" endpoint. Our backend is hosted on AWS (laravel vapor).

So if we assume that the up-time is equal, what are the pros and cons using AWS EventBridge?

Thanks in advance

BR

Mads

[james-langille · Accepted solution]

Hello, @Mads-Storebuddy! Welcome to the community.

The main advantage of using AWS EventBridge (or Google Pub/Sub) over classic "self-managed"/http endpoints is that your app can consume webhooks at it's own pace, so if a bunch of webhooks come in a burst, we can easily deliver them all to EventBridge even if your app consumes webhooks at slower rate than we can deliver them. This has definitely been an issue with some apps that use HTTP in the past.

The downside of using EventBridge is that you need to manage the queue yourself. However, if you're already using the AWS infra, it shouldn't be a problem.

Hopefully this helps!