trigger.dev VS sdk-java

[TRI-1401] feat: Add support for tabler-icons when using the `icon` for Tasks #616

thanks a lot james! you guys pioneered the video bounty use case, was so impressive seeing 10 videos submitted in just a single day!

https://github.com/triggerdotdev/trigger.dev/issues/249

- Support for Background Functions – we deploy your code so you can run any length of task. You write the code like any other job in your codebase. Discussion here: https://github.com/triggerdotdev/trigger.dev/discussions/400

9. Listen - Trigger.dev

Trigger.dev (YC W23) is the open source Background Jobs framework for Next.js. You can create long-running Jobs directly in your codebase with features like API integrations, webhooks, scheduling and delays. And today you can use their one-click integration to trigger anything from a database change in Supabase.

Trigger.dev is fully open source and can be self-hosted. We have a cloud product too.

We built a beta version of Trigger.dev in a few months

How does this compare against Temporal/Cadence/Conductor? Does hatchet also support durable execution?

https://temporal.io/

Flawless sounds a lot like https://temporal.io/ .

I'm wondering if it has the same scalability concerns - sticking everything in Postgres is fine at small-ish scale, but what happens when you outgrow Postgres, either because you have higher availability requirements (can't handle primary DB restarts) or because of the sheer volume of the workload?

Temporal is a scalable and reliable runtime for durable Workflow Executions. It enables you to develop as if failures don't even exist. I started exploring it over the Christmas holiday and using it for a recently open-sourced project.

I have my eyes on https://temporal.io/ for similar purposes.

Check out temporal.io open source project for a much cleaner solution using Durable Execution abstraction.

Interesting to see Netflix featured both on StackStorm & https://temporal.io/ frontpages.

Our stack at Escape is written in multiple languages because each team has specific needs. We use TypeScript for its vibrant ecosystem, Python for cybersecurity research and Go for performance-sensitive tasks. To orchestrate cross-language task orchestration, we first developed a simple request-response protocol over HTTP, but it wasn't sustainable as the Escape codebase grew rapidly. We evaluated several technologies to replace our homegrown protocol, and two emerged as the most promising options: Connect and Temporal. The title gives it away, but the reason is far from obvious

I've put a lot of time into Airflow and feel similarly that it's a huge pain and a risk to rely on it. I've replaced it with Temporal (https://temporal.io/) and while I don't have the breadth of experience with the frameworks you listed, I do think Temporal is a great replacement for Airflow.

Just to confirm my understanding; would you consider at least part of your product offering to be similar to temporal.io [1]? Your examples are reminiscent of theirs.

[1] https://temporal.io/