I want to point out one additional structure that could have worked:
You can have Orders Service publish to an SNS Topic and then have multiple SQSs subscribed to the topic. The SQSs can then invoke their specified Lambda.
SQS provides the durable transport and is Lambda aware; SNS provides the fan-out capability of the event. SNS offers event filtering capabilities on subscription that matches Event Bridge's capabilities.
Don't get me wrong, Event Bridge is a great product for this. Just always be aware of the latency and throughput limits Event Bridge imposes that doesn't make it ideal for some use cases.
Agreed on this, thanks Danny. I'll update the post to take this into account. The throughput limits of EventBridge really does limit its usage for workloads with millions of events per day
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I want to point out one additional structure that could have worked:
You can have Orders Service publish to an SNS Topic and then have multiple SQSs subscribed to the topic. The SQSs can then invoke their specified Lambda.
SQS provides the durable transport and is Lambda aware; SNS provides the fan-out capability of the event. SNS offers event filtering capabilities on subscription that matches Event Bridge's capabilities.
Don't get me wrong, Event Bridge is a great product for this. Just always be aware of the latency and throughput limits Event Bridge imposes that doesn't make it ideal for some use cases.
Agreed on this, thanks Danny. I'll update the post to take this into account. The throughput limits of EventBridge really does limit its usage for workloads with millions of events per day