Are there any AWS gurus out there that would be ab...
# help
j
Are there any AWS gurus out there that would be able to provide me with resources / info on how I could accomplish a job queue / processing system using AWS? (I'm thinking SNS/SQS?) I'm just not sure how the interaction should work with the project I have in mind where a user uploads an excel file via a frontend, the job is created and the excel file is processed and the rows are looped through and some API calls to a 3rd party service are executed as a job (via lambdas?) with other jobs (either using the same process or different types of jobs) and then when the job is complete maybe a notification can be sent to a frontend. Is this the right sort of process for the project? I'd like it to be fairly scalable and wont really know much about the throughput until it's in action. Any thoughts, info, ideas or pseudo-code would be very appreciated. I'm a young dev still learning much about the AWS platform 😄
m
You should look seriously at step functions for this.
Step Functions orchestrate your lambda functions or other AWS services. SST adds nice tooling for building it out. If you don't have prior experience with step functions, I wrote a blog post a while back that might help you understand => https://dev.to/elthrasher/exploring-aws-cdk-step-functions-1d1e
j
Looks interesting, I've heard of step functions before and I have tried to use them with SST but only just as a test, any idea how i'd structure this sort of project with Step Functions in SST? I think the thing that confused me when trying them out before was the input and output paths, wasn't sure how to pass data between lambdas etc
m
The intent of the blog post was to show that. SST is very helpful here for having a fast dev turnaround and when they bring the console back, it's hugely helpful as you can see the inputs and outputs of each function.
m
you can also consider this flow: lambda -> s3 -> second lambda