This is how you can run async jobs in Next.js with server actions

[@SeibertSwirl]

Good job babe!!! Also 160k that’s awesome! I’m so proud of you ❤

[@PraiseYeezus]

How much have you learned about web development just from watching the videos and talking to Cody? You guys are goals lol

[@shubhamrasal8930]

Thanks for the tip man! I had an issue similar to this where I had to wait for a blockchain transaction to confirm. I just wrapped it into an async call and now I update the UI appropriately.

[@Nurof3n_]

one extra case you should handle with this approach is if the lambda is being killed before it finishes processing, maybe set a timeout and rerun job or set as failed. I know it doesn't happen often but it's annoying when it does, that's why I use inngest to handle async jobs (but like you said it adds complexity and cost)

[@usman3c]

Congratulations on 160k 🎉🙂

[@codinginflow]

This looks really cool. So these server actions do execute concurrently?

[@WebDevCody]

It seems like it, but I guess it depends on where you deploy

[@PraiseYeezus]

Would love a video about how you do local AWS development. Besides from deploying to Amplify, I find AWS feels way more complicated than just using a library to call an API with proper credentials

[@teamvashmmo3218]

He uses SST and has made lots of vids about it

[@Peacemaker.404]

hey cody great video and i have a question does this app work for videos with chapters and those without? For instance, this particular video has chapters but some doesn't or it generates chapters from scratch based on transcripts?

[@WebDevCody]

It uses the transcripts to generate chapters, so it doesn’t use existing chapter knowledge at all

[@Peacemaker.404]

@@WebDevCody thanks for replying, i use yt-dlp.

[@AndreasStraub]

Cool, i thought the function would be interrupted in Nextjs after return. Good to know. But can you really always rely on it, that that the background function is not being interrupted? By the way: the react-query has a build-in poling feature. Don’t need to use a custom setInterval stuff

[@WebDevCody]

I think it’s because the server action returns the data to the client but the JavaScript promise will still stay on the event queue even after returning the response.

[@rajusharma823]

Yeah that was a great analogy 😅

[@IvanRandomDude]

Isn't using serveless for things like this bad idea? Lambdas will be long running and that's what costs the most, compute time.

[@WebDevCody]

It’s a bad idea when it becomes a cost problem. For most apps it won’t be

[@rand0mtv660]

That's an interesting idea, but as you mentioned something more robust or reliable would probably have to be implemented in the long run. Btw, I thought you switched to Remix and moved away from Next.js. How come you are using Next.js again? Did I miss a video of you explaining why you stopped using Remix?

[@WebDevCody]

I still like remix, but at this point I just rather stick to the framework I’m familiar with so that I don’t have to keep context switching on my side projects. It’s annoying working on a next project and then switching to a remix one back and forth

[@rand0mtv660]

@@WebDevCody ok yeah makes sense. Probably way more productive that way.

[@kecserto]

I think this is an awesome usecase for SSE (push updates to the UI, showing the current step of processing the video, handling errors). Probably not that easy to implement with next's app router tho I am not sure about that.

[@jakubmatousek9429]

Simple pooling is absolutely fine, just keep an eye on the performance as your user base grows. Once it's necessary becouse of reasons, re-implement. Most likely, there won't be reasons.

[@MrTadsuki]

Do you mind sharing your vscode theme and font?

[@reubence_]

Question: Wouldn't something like React-Query pull in optimistic data changes automatically?

[@WebDevCody]

That would help with the initial delay between hitting the button and waiting for the job to finish, but regardless we need the api response to be fast so we can get the job id otherwise we don’t know what to refresh

[@neociber24]

Doesn't NextJS kill the job when you refresh the page? I didn't know we can let the lambda run like that.

[@WebDevCody]

I’d need to verify, but I don’t remember it killing the request

[@freqbac1548]

What theme extension are you using? Thanks for the videos.

[@WebDevCody]

Bearded theme stained blue

[@DouglasSouza-wo9rp]

you can share your json user settings?

[@ayushgogna9732]

back to nextjs ? from remix

[@medAmineRg]

thats why everyone should know the architecture of languages before start coding.

[@iSnakeBuzz]

protip: With cloudflare workers you have websockets at the edge.

[@WebDevCody]

Oh nice

[@drewbird87]

websprockets 😁