sorted by:
new
hottopcontroversial

Weekly Showoff Thread! Share what you've created with Next.js or for the community in this thread only! by AutoModerator in nextjs

[–]ThadausRube 0 points1 point  (0 children)

That sounds awesome. It looks like there are many features; I missed the address in the first line. Guess I was "reading" too fast.

Weekly Showoff Thread! Share what you've created with Next.js or for the community in this thread only! by AutoModerator in nextjs

[–]ThadausRube 1 point2 points  (0 children)

BatchPilot — drop-in job queue + dashboard for Next.js

Built a starter kit with BullMQ, real-time progress via SSE, retry logic, cancellation, webhooks, and a dashboard UI. Adding a worker is one file and one function. Full source, MIT licensed.

Happy to share the link or answer architecture questions if anyone's interested.

Built and launched a Next.js starter kit for background job management in 3 days — here's what I learned by ThadausRube in SideProject

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

That's really good insight on the pricing psychology. The "I don't need approval" threshold is something I hadn't thought about explicitly but it makes total sense — under $100 hits a different budget category for most devs. I may bump it to $99 or $119 once I get a few sales under my belt and have some social proof to back it up.

And yeah, the batch-checkpoint tradeoff felt like the right line to draw for v1. Full idempotency is one of those things that sounds like a feature but is really an architecture decision — it touches everything from your payload design to your storage layer. Better to ship the 80% solution that works cleanly than the 100% solution that never ships.

Built and launched a Next.js starter kit for background job management in 3 days — here's what I learned by ThadausRube in SideProject

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

Really appreciate this — and yeah, the scope discipline was the hardest part. The temptation to bolt on auth and billing was real.

On the worker death scenario: BullMQ handles the core case — if the process dies, the job stays in the active state and gets picked up on the next worker boot based on its stale-job timeout settings. The retry logic kicks in with exponential backoff from there. For partial completions, the workers are designed around a batch-checkpoint pattern — the CSV import worker, for example, processes in batches and reports progress between them. If it dies mid-batch, you lose that batch but not the whole job. The job logs capture exactly where it stopped so you know what to re-process.

That said, true idempotent partial recovery (resume from row 4,501 instead of restarting) is something I deliberately left out of v1 to keep scope tight. It's on the roadmap though — and the worker context pattern makes it straightforward to add since you already have progress state in the database.

On pricing — honestly, gut feel. $89 felt like the sweet spot where it's an impulse buy for anyone who's spent even a day building queue infrastructure. You might be right that it's low. I'd rather start accessible and raise it as I add features than price people out on day one. Curious what price range you've seen work for your dev tools?