How does it compare to other projects

[maelp]

Very interesting project, I'm wondering how it compares to something like DBOS (integrated in Postgres) or Inngest (separate process, more complex, but with dashboard, etc)?

[tomasol]

Good call, I need to write a comparison on the website. In short it compares to temporal - but without the usual footguns. Using hashmaps is 100% deterministic here. Attempting to spawn a thread is a compile error.
Looking at Inngest - Obelisk workflows are regular functions with no callback hell on every step. Instead, every child execution call acts as if there was a breakpoint hit. The parent execution is paused, waiting for result. If the result does not come within lock timeout, the parent execution will be re-executed with all previous steps replayed.
As for the performance, it can execute more than 1400 small executions per second on a laptop.

[tomasol]

I wrote two blog posts about this topic:

• Challenging the Fastest OSS Workflow Engine - WindMill
• Comparing Obelisk with DBOS

Let me know if there is interest in writing more of these.

[xeoncross]

I'm looking forward to it, I am especially interested in the comparison to github.com/temporalio/temporal given the number of small companies and solo devs who use it (being OSS).

[tomasol]

Please check out Comparing Obelisk with Temporal and Restate