Temporal workflow vs Cadence workflow

Question

How is temporal.io related to cadenceworkflow.io? What should be used if starting a new project depending on the cadence workflow service?

Answer 1

My personal opinion, not from Uber, but just as an outside contributor to Cadence project.

It’s quite a pity that the project is divided into two, including the community. Temporal is a great project/team/company. I wish Temporal have great a success.

Sometimes it’s good for the wold to have some competition. The fact is both are under active development. You can see they have some different focuses if looking at their road maps. The two projects share the same vision to let everyone rethink about programming models of long-running business.

I understand that at this moment, it’s quite hard to say which one is better, because temporal just forked from Cadence. But over the time the projects will diverge and eventually the answer will be clearer like MySQL/MariaDB, or Cassandra/Scylladb, or even MongoDB community version / commercial version.

I personally leaning to Cadence, because of the support from Cadence team, and most Cadence contributors are still here, and I always believe in the great team work from Cadence team members. And also obviously because I am spending more time over there.