temporal

So is https://github.com/obeli-sk/obelisk the Rust version of https://github.com/temporalio/temporal (Go)? Can you guys add a comparison between them on the site?

Since I'm in a ranting mode -- here's a good example: you're limited to _ONE_ IO per shard in the history service: https://github.com/temporalio/temporal/blob/e22e6304b3c4a409... https://github.com/temporalio/temporal/blob/e22e6304b3c4a409... Temporal does a crazy amount of database operations and all of these are behind that mutex. Oh, and you can't change the shard count on existing clusters. Great stuff.

Temporal employee here. I'm very surprised by your comment. It's true that we recently had a Series D and that VC firms recognize the value of what we do. The Temporal Server software is 100% open source (MIT license: https://github.com/temporalio/temporal/blob/main/LICENSE). It's totally free and you don't even need to fill out a registration form, just download precompiled binaries from GitHub or clone the repo and build it yourself. You can self-host it anywhere you like, no restrictions on scale or commercial usage. We offer SaaS (Temporal Cloud), which customers can choose as an alternative self-hosting, based on their needs. The migration path is bi-directional, so not a trap by any definition. Regarding AI, Temporal is widely used in that space, but that does not negate the thousands of other companies that use Temporal for other t

i’m not associated with temporal, nor does the link above have any referrer nonsense in there. i don’t profit from referring to it here. in fact it may well be a household name in the hn community. that out of the way, it’s not wrong to point to a proper resource that can explain and demonstrate my argument better than a couple of words could. temporal is open source[0] so maybe a github link would have been more palatable? [0]: https://github.com/temporalio/temporal

https://github.com/temporalio/temporal/tree/v1.27.2 (MIT) It has been submitted quite a few times but I don't readily see any experiences (pro or con) https://news.ycombinator.com/from?site=github.com/temporalio

Just for clarification, So you can't really host this without open-sourcing my product (since your server is AGPL). Isn't it a stretch to call this really open-source? I compare this to something like a temporal which I can self-host without worrying (and which I believe is MIT license [https://github.com/temporalio/temporal/blob/main/LICENSE])

Temporal's go is... something. They used to use Java (I think), then they switched to Go, and the Go is very Java-like. Or maybe I just don't know Fx. https://github.com/temporalio/temporal/blob/main/service/mat... The issue we hit with Temporal - again and again - is that it's very under-documented, and it's something you install at the core of your business, yet it's really hard to understand what is going on, through all the layers and through the very obtuse documentation. Maestro has... no documentation? OK Temporal wins by default.

Is Temporal still alive? (website doesn't resolve for me) EDIT: I found the GitHub page https://github.com/temporalio/temporal

I don't know if I agree with the argument regarding durability vs elastic execution. If I can get both (with a nice API/DX) via something like Temporal (https://github.com/temporalio/temporal), what's the drawback here?

Correct, the workflow's guarantee to always complete executing independent of process/hardware failures is dependent on the database not losing data. You host your workflow code with Temporal's Worker library, which talks to an instance of the Temporal Server [1], which is an open-source set of services (hosted by you or by Temporal Cloud), backed by Cassandra, MySQL, or Postgres. [2] So for instance increasing Cassandra's replication factor increases your resilience to disk failure. [1] https://github.com/temporalio/temporal [2] https://docs.temporal.io/clusters#persistence

I think this is the link to cadence: https://github.com/uber/cadence and temporal: https://github.com/temporalio/temporal