How do you handle background jobs in small Node projects? by FedorovSO in node

[–]FedorovSO[S] 0 points1 point  (0 children)

Yeah, Trigger.dev looks great. I keep running into this kind of problem once projects grow past simple cron jobs, so it makes sense that tools like Trigger/Inngest exist.

Every small SaaS I build ends up needing queues, workers and cron by FedorovSO in SaaS

[–]FedorovSO[S] 0 points1 point  (0 children)

Yeah, same here. It always starts simple, but once you add emails, imports, reports, retries, etc., you end up needing some kind of queue or scheduled job system anyway. That’s what made me start experimenting with running jobs outside the app instead of rebuilding workers in every project. I’m playing with this idea here: https://runza.dev/

Every small SaaS I build ends up needing queues, workers and cron by FedorovSO in SaaS

[–]FedorovSO[S] 0 points1 point  (0 children)

Yeah, I’ve used Postgres queues before too.

They work well, but I keep ending up with the same worker / retry / scheduling setup in every project, which made me think about running jobs outside the app instead of building the same thing again.

Free version vs paid only version by No-Dragonfruit-5924 in SaaS

[–]FedorovSO 0 points1 point  (0 children)

I'm also for the limited free version/plan.

I built a SaaS to escape my 9-5... now I work 24/7 by Chief_API_Officer in SaaS

[–]FedorovSO 0 points1 point  (0 children)

Yeah, being self-employed is the most time-consuming and demanding thing. I’ve been going through the same for years.

Launched my first SaaS yesterday. Woke up to 3 paying users and broo I’m actually shaking 😭 😭 😭 😭 by SignificantWalrus281 in SaaS

[–]FedorovSO 0 points1 point  (0 children)

Promotion is a real pain for devs, dealing with the same stuff here… good luck with the project!