Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Support Aws EventBridge #3490

Open
honkuan86 opened this issue Jan 24, 2025 · 3 comments
Open

[Feature] Support Aws EventBridge #3490

honkuan86 opened this issue Jan 24, 2025 · 3 comments
Labels
0 - Backlog feature request .NET Pull requests that update .net code V10.X

Comments

@honkuan86
Copy link
Contributor

Discussed in #3474

Originally posted by honkuan86 January 14, 2025
Hi,

I would like to discuss about adding Aws EventBridge support to Brighter.

I'm looking is it possible to publish events to Aws EventBridge using Brighter, since EventBridge is using a different approach than SNS (without a Topic).

Any feedbacks would be greatly appreciate. Thank you.

@lillo42
Copy link
Contributor

lillo42 commented Jan 29, 2025

Hey @honkuan86 why do you want support for EventBridge? For Scheduler message (If so we are working on this for V10)?

@iancooper
Copy link
Member

The key thing to understand on AWS EventBridge is push vs. poll. You can poll from EventBridge, but you can't push to it, say from SNS. But, you can publish from Brighter to an SQS queue, and then EventBridge can read from that queue.

However, if we want to avoid an extra queue, we could use the HTTP interface, and put an event onto EventBridge that way.

I suspect that is what folks want - push to EventBridge without using an SQS queue.

https://docs.aws.amazon.com/sdk-for-net/v3/developer-guide/csharp_eventbridge_code_examples.html

I think we could add that as a transport. It would only really cover the producer though, as the consumer would just be an AWS queue. So it might make sense to add it into the existing AWS client as an alternative producer target. As we now let you choose between SNS and SQS, I guess it might make sense to allow you to choose Event Bridge.

@iancooper iancooper added 0 - Backlog feature request v10 Allocal to a v10 release .NET Pull requests that update .net code labels Feb 26, 2025
@honkuan86
Copy link
Contributor Author

hi @iancooper , what you are suggesting is to add the AWS EventBridge as an alternative producer in the existing MessagingGateway.AWSSQS right ?

@iancooper iancooper added V10.X and removed v10 Allocal to a v10 release labels Mar 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - Backlog feature request .NET Pull requests that update .net code V10.X
Projects
None yet
Development

No branches or pull requests

3 participants