I am researching various workflow engines for integrating it into our application and Cadence/Temporal has caught my eye as something that I really want to like and pursue, but the “Alpha” release status kind of scares me a little.
From what I understand, the core of the Temporal is based on the very stable Cadence workflow engine that is being actively used in production by many companies already. To the best of my understanding, the main change that Temporal has over Cadence Workflows is that in Temporal, workflows and activities use gRPC + Protobuf to communicate with the workflow server while Cadence used TChannel + Thrift, plus there are some other improvements in the Go and Java APIs for workflow and activity definitions.
On the workflow state persistence side, Cadense uses Cassandra whle Temporal has added support for MySQL (and soon PostgreSQL as well). With possibility to add more SQL engines.
So, in order to better understand what kind of a gun I am pointing at my proverbial foot, I would like to understand little bit more about what is current state and near term plans for Temporal.
Given that most of the base of the Temporal has carried over from Cadence, would you say that there are no obvious technical issues when deploying Temporal to production and running some workflows on it in near term future (Q4 of 2020)?
What is still missing from Temporal implementation before Temporal team is ready to remove Alpha label from Temporal releases (promoting it to Beta?). And when do you expect to reach that point?
2.1. Similar question about the Beta.
2.2. I guess what I want is some sort of rough roadmap to version 1.0
How and in what way can community get involved? If I choose to adopt Temporal while it’s still in Alpha is it possible to open pull requests to fix issues that we find? What is the process for contributors?
What kind of support can Temporal team provide, if we find ourselves facing issues that we do not know how handle?