QStash vs Custom Solution?
Hi all,
In an app I'm building, I have a use case where Vercel is offloading some more complex processing to an AWS Lambda function via the JS SDK. Currently, the Vercel serverless function is waiting for the Lambda function to return as the return value contains needed data.
With this solution, I have been running into issues regarding Vercel funciton timeouts (on the pro plan).
In my research on how I could fix this, I came across QStash which looks like a very good product and I think it would solve my issues, but it also got me thinking whether I would need it at all.. Would it be feasible for the Vercel function to call the Lambda function then exit, then the Lambda function send its return value to an API endpoint on my app for the further processing required?
I've never built functionality like this before so there may be more to it than I can currently see, but in my head this should work, are there any obvious problems going with my proposed "custom" solution?
In an app I'm building, I have a use case where Vercel is offloading some more complex processing to an AWS Lambda function via the JS SDK. Currently, the Vercel serverless function is waiting for the Lambda function to return as the return value contains needed data.
With this solution, I have been running into issues regarding Vercel funciton timeouts (on the pro plan).
In my research on how I could fix this, I came across QStash which looks like a very good product and I think it would solve my issues, but it also got me thinking whether I would need it at all.. Would it be feasible for the Vercel function to call the Lambda function then exit, then the Lambda function send its return value to an API endpoint on my app for the further processing required?
I've never built functionality like this before so there may be more to it than I can currently see, but in my head this should work, are there any obvious problems going with my proposed "custom" solution?
