Hi, I'd like to build a event driven application using Lambda's and Event Bridge. Upload Lambda functions that listen and pull events (messages) off Event Bridge, do some work, then put new events back onto Event Bridge. Is SST the right fit for this? The docs describe API, Auth, Storage, Database, Frontend, Cron - but I don't see just a plain old Lambda that can read/write msgs from Event Bridge.

Hey Rudi, SST would be great for this! As a matter of fact, there is a tutorial for using EventBridge and Lambda. Checking out the example code is pretty straightforward:

$ npm init serverless-stack --example eventbus
# Or with Yarn
$ yarn create serverless-stack --example eventbus

Ah nice, got it! Thank you very much, exactly what I was looking for.

Exactly!

Most of our app is built like this (apart from APIs). Some other things to consider: • Put an SQS queue in between EventBridge and lambda - you can have an EB rule with SQS as a target. It adds the ability to batch process, retries and DLQs • Have your DB publish events to EventBridge • Use EventBridge to communicate between services/pipelines, and SQS or StepFunctions to orchestrate within a service/pipeline

@Omi Chowdhury The SQS queue addition is interesting. I'm just exploring so I'll start with 100% EB (demo follow along), then add the SQS on after - learn by doing.

just an fyi we do have an eventbridge construct

@thdxr Hmm, so something like the Lambda pulls the message from the queue - but if it fails it won't confirm the msg is processed back to SQS, thus the message is still on the queue ?

Yeah and you can set some configuraiton on the queue to configure how long it stays there + sending it to a dead letter queue after some time

Use this strategy for both "normal" lambdas and also step functions (multi lambda) ?

With step functions you can create your own retry logic within the state machine so maybe less important there