You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An end-to-end example to write workflows to download a file, zips it, and uploads it to a destination.
36
35
37
36
An important requirement for such a workflow is that while a first activity can run
38
37
on any host, the second and third must run on the same host as the first one. This is achieved
39
38
through use of a host specific task list. The first activity returns the name of the host
40
39
specific task list and all other activities are dispatched using the stub that is configured with
41
40
it. This assumes that FileProcessingWorker has a worker running on the same task list.
41
+
42
+
43
+
## Differences between Java and Golang Clients
44
+
45
+
While many features are already supported in the Cadence Golang client, some features are missing in the Java client. The Cadence development team aims for feature parity between the two clients, with new features typically being implemented in cadence-go-client first.
|**Up to Date Samples**| Supported | No |[Link](https://github.com/cadence-workflow/cadence-java-samples/issues)|
52
+
|**Customer provided context propagator**| Supported | No ||
53
+
|**Poller autoscale**| Supported | No ||
54
+
|**Auto heartbeat[^auto-heartbeat]**| Supported | No ||
55
+
|**Jitter start**| Supported | No ||
56
+
|**Sessions (sticky activity workers)[^sticky]**| Supported | No ||
57
+
|**List all queries supported for a given workflow**| Supported | No ||
58
+
59
+
60
+
[^auto-heartbeat]: heartbeating in java is simple to implement and might be better for end user to determine which type of heart beating is better for the use case rather than add a generic auto-heartbeat mechanism to the client.
61
+
[^sticky]: feature needs more traction in order to prioritize
0 commit comments