i have long running background task in my web app tech stack is next js and vercel.
i wanted to return an instantaneous response to frontend then send real time updates to server .
so i used upstash qstash and pusher with qstash i perfomed parallel processing to prevent vercel serverless function timeout error . but i easily exceed qstash daily limit so i tried using fire and forget with fetch() by fetching other api routes from fetch this works but there is no way to check if all small serverless function got executed properly .
Should i implement my own message queue any message queue service or way around this ?
i tried using trigger.dev they had a very high latency since my web app requires me to fetch entire github repo code using parallel processing but trigger.dev had so high latency that even entire web app seemed to be frozen. I also tried using external express api but even express api deployed on render have timeout limit
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
i have long running background task in my web app tech stack is next js and vercel.
i wanted to return an instantaneous response to frontend then send real time updates to server .
so i used upstash qstash and pusher with qstash i perfomed parallel processing to prevent vercel serverless function timeout error . but i easily exceed qstash daily limit so i tried using fire and forget with fetch() by fetching other api routes from fetch this works but there is no way to check if all small serverless function got executed properly .
Should i implement my own message queue any message queue service or way around this ?
If your background task takes a long time to process, you might want to try Trigger.dev.
They also have a setup guide for Next.js: trigger.dev/docs/guides/frameworks....
i tried using trigger.dev they had a very high latency since my web app requires me to fetch entire github repo code using parallel processing but trigger.dev had so high latency that even entire web app seemed to be frozen. I also tried using external express api but even express api deployed on render have timeout limit