Coming to Next.js from Laravel, being able to hand things off to a long running worker is one of the things I missed the most. We're currently handling this with a non-ideal solution and will definitely check Trigger.dev out when you launch that feature.
May I ask what made you to switch from Laravel to Next.js?
Show HN: Trigger.dev V2 – a Temporal alternative for TypeScript devs
41–44 of 44 posts
Re: Show HN: Trigger.dev V2 – a Temporal alternative for TypeScript devs
#42How does it compare to inngest.com?
Chiming in as a founder of Inngest. We released our TS SDK a year ago so had quite a head start in this area. The approach in their V2 release makes them more similar to us, though there are still some large differences, including the fundamental architecture, queueing technology, scale, etc. Some differences you'll notice as a developer: - Concurrency and parallelism. We allow you to run steps in parallel, configure…
Re: Show HN: Trigger.dev V2 – a Temporal alternative for TypeScript devs
#43The marketing landing page looks very similar to Vercel's homepage. https://i.imgur.com/o5Cdldv.png
If anything they have a cool slider/tabs for different actions.
Re: Show HN: Trigger.dev V2 – a Temporal alternative for TypeScript devs
#44My initial thought when opening your website was that this was a job queue, like BullMQ. Not a "link things together like IFTT/Zapier/N8N but in code" platform. I don't think I'd use "Background Jobs framework" to describe what you're building, as that term has very different associations. Am I right in saying this is like BullMQ, except with integrations? If so, I'd focus more on the integration part of your marketi…
That's really interesting. What associations do you have with "Background Jobs framework"? Quite a lot of our customers are using us instead of Temporal. Not for linking stuff together use cases.