Hey Guys,
I am new to AWS Eventbridge and I am currently dealing with how to handle negative scenarios in EventBridge. I am currently dealing with microservices architecture, and I am in need of solutions for the following questions:
How to handle negative or no response from Event Bridge
When there is no response from a a service when event bridge tries to notify should the service owner take responsibility or should we use single or multi lambda
Creating a queue named DL Queue with a lambda is something I found when googled, but is there any better cost effective solution ( Lambda seems to be more costlier as far as I explored )
If an event is triggered and if the request body is itself improper & it keeps trying for 24 hours, is there anyway we can manually clear the events in event bridge
It would be very helpful if some insights were given on these
Top comments (1)
There are a few different ways to handle negative or no response scenarios in AWS EventBridge, depending on the specific situation. Here are a few suggestions:
When there is no response from a service when EventBridge tries to notify it, you can use a dead letter queue (DLQ) to store the failed events. This allows you to retain the failed events for later analysis and retry, if necessary. You can create a DLQ by using the AWS Management Console, AWS CLI, or AWS SDKs.
If you want to take responsibility for handling failed events, you can create a Lambda function that is triggered by the DLQ and processes the failed events. This allows you to implement custom logic for handling the failed events, such as retrying the failed events or sending notifications to the service owner.
Instead of using a Lambda function to process the failed events, you can also use an Amazon SQS queue as the DLQ and process the failed events using a worker tier or other background processing solution. This can be a more cost-effective solution than using a Lambda function, depending on the specific requirements of your application.
If an event is triggered and the request body is improper, you can use an event pattern to filter out invalid events. An event pattern allows you to specify a set of conditions that incoming events must match in order to be delivered to a target. This can help prevent EventBridge from trying to process invalid events for 24 hours.
If you need to manually clear events in EventBridge, you can use the AWS Management Console, AWS CLI, or AWS SDKs to delete the events from the event bus. This can be useful in situations where you need to clean up test events or events that have been stuck in the event bus for some reason.
Overall, the best approach for handling negative or no response scenarios in AWS EventBridge will depend on the specific requirements of your application. You may need to experiment with different solutions and choose the one that works best for you.
I'm an experimental help bot that leverages ChatGPT. As such, the answers I provide may be incorrect, incomplete, or even nonsensical. I am not associated with OpenAI.
Please reply to my comment(s) with your own corrections and feedback.