matt-aitken

6 ms·

1.
by matt-aitken 1y ago
You can be remote as long as your timezone is between UTC -2 and UTC +8. That covers most of Europe, Africa, and all of North and South America.
2.
by matt-aitken 1y ago
Inngest is very similar to Trigger.dev version 2: it’s an API for queuing and orchestrating workflows. You need to divide your work into steps, where each step needs to have serializable inputs and outputs, and takes less than the timeout o
3.
by matt-aitken 1y ago
Yep you do need to be careful with uncaught errors. When you setup your project you choose the default number of retries and back-off settings. Generally people don't go as high as 50 and setup alerts when runs fail. Then you can use t
4.
by matt-aitken 1y ago
The core is a durable execution engine, but there's a lot more needed to build good applications. Like being able to get realtime progress to users, or being able to use system packages you need to actually do the work (like ffmpeg, br
5.
by matt-aitken 1y ago
We support this but you do need to pass a public access token to your frontend so it's secure: https://trigger.dev/docs/realtime/react-hooks/triggering
6.
by matt-aitken 1y ago
Yep, thanks Mintlify!
7.
by matt-aitken 3y ago
Thanks! Do you want the ability to call a Job from inside another Job and wait for the result? We have a discussion about that here, would love to get your input: https://github.com/triggerdotdev/trigger.dev/discus
8.
by matt-aitken 3y ago
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.
9.
by matt-aitken 3y ago
Inngest is also an easier to use version of Temporal, for serverless. Currently the major differences are: - Open source: we're fully open source and self-hostable with Apache 2 license. - API Integrations: we're building first cl
10.
by matt-aitken 3y ago
Part of the inspiration for this was Firebase functions. We used them extensively on a previous project with their Firestore triggers. There's a lot to like about them but it was a messy development experience, especially the deploymen
11.
by matt-aitken 3y ago
Great, you can subscribe to updates on our discussion here: https://github.com/triggerdotdev/trigger.dev/discussions/400 We'll be updating it as we make progress and open it up for early testers.
12.
by matt-aitken 3y ago
Our focus is on writing jobs in your existing codebase. That means you use your existing development workflow (code editor, version control, etc) and can access your database and existing code easily. I'd also say that Windmill, and ot