Best place in AWS for a long running subscription background service

Question

I currently am trying to set up a system in AWS that utilises EventSourcing & CQRS. I've got everything working on the Command side, and this is storing the events into Aurora. I've got SqlEventStore as my EventSourcing store and that has a Subscription mechanism that will listen for new events and then fire a function appropriately.

So far it's all set up in Lambda, but I can't have the subscription in Lambda as they aren't always running, so my first thought was running this side in Fargate and a docker container. Using my reading though, this seems to need to be fired by a task, rather than sit in the container on a subscription.

So my question is really, where is best to have a long running process in AWS that just sits listening for things to happen, rather than responding to a prod from something like a Lambda.

Answer 1

So my question is really, where is best to have a long running process in AWS that just sits listening for things to happen, rather than responding to a prod from something like a Lambda.

I will suggest to go with Fargate or EC2 type ECS container, with fargate you do not need manage server, something similar to lambda but more suitable for such long-running process.

This seems to need to be fired by a task, rather than sit in the container on a subscription.

no, you can run fargate in two ways.

• Running as a long-running services
• fire service based on cloud watch event or schedule time ( perform task and terminate)

AWS Fargate now supports the ability to run tasks on a regular, scheduled basis and in response to CloudWatch Events. This makes it easier to launch and stop container services that you need to run only at certain times.

AWS fargate

Where is best to have a long-running process in AWS that just sits listening for things to happen, rather than responding to an event from something like a Lambda

• If your task is supposed for the run for a long time then lambda is not for you, there is always timeout in case of lambda.
• If you do not want to manage the server, and the process is supposed to run for a long time, then fargate is for you, so then it's fine to sit for the event and listen.

Answer 2

you can explore aws glue python shell for long running server services.