would it be reasonable in my step function, after I page a chunk of items from a dynamodb to asynchronously (i.e. not wait for a response) call a SQS consumer to do further downstream processing.
The reason basically is so that I can use a SQS consumer to to an async.parallel to pass each item in the chunk to a worker - thus allowing me to do some big jobs for each element of the chunk in parallel. (like this https://cloudonaut.io/integrate-sqs-and-lambda-serverless-architecture-for-asynchronous-workloads/)
Obviously when my calling step function finishes it has no idea of how things will finish up on the SQS side but maybe i can handle that over in the consumer side.
The SQS timeout window would probably be high since each worker has to do a lot of work for each element passed to it by the SQS consumer
Would be great if step functions offered an ‘Array-Parallel’ state stype