What are some of the big differences in Java Client versus Go Client when implementing Uber Cadence workflow?

Question

I am working on designing a workflow with the intention of using cadence workflow engine and Java client. Seems like uber is actively using Go, and thus Go has better documentation and Activity and other classes than Java Client. Is this true?

Answer 1

If you go the the java-client channel in Cadence slack, the community has more discussion than go-client. Even in Uber, Java-client is heavily used by core services like payments.

Go client happens to have more docs/samples because it started a little earlier. In fact, the docs that are missing in Java, could be derived from Go. It should be noted that there are more documents in Java library. For example, the documents of how to write unit tests, instead of putting in to cadenceworkflow.io, we put in javadocs directly. Because this is the convention for Java developer to lookup documentation.

IMO they are the same important for Cadence. All the new features are implemented/rolling out at the same time hence they don't have real difference.

Answer 2

No, it is not really true. The majority of the open source users of Cadence and Temporal are using Java SDK.