Closed samarabbas closed 2 years ago
Hi, do we have any ETA on this? Thanks!
@samarabbas
We are targeting alpha release of the gRPC version of Cadence in February.
@mfateev Great, thanks Maxim!
Does this mean that Cadence workers will be able to communicate with the frontend over gRPC?
We need this to be able to run workers outside of the Cadence cluster.
@BartXZX Yes. The workers are going to talk to the cluster through gRPC.
Good day, Do you have an update on the ETA for this?
Thanks in advance
We ETA is within two weeks for the alpha release.
Just curious about this.
Looking forward to this!
Hi any updates on this ?
We ETA is within two weeks for the alpha release.
Hey Maxim is there any updates on the migration to grpc? Thanks!
@tonyabracadabra Temporal V1 was released last month with grpc support: https://docs.temporal.io/blog/temporal-v1-announcement
@tonyabracadabra Temporal V1 was released last month with grpc support: https://docs.temporal.io/blog/temporal-v1-announcement
Thanks! Is temporal a complete replacement for cadence right now with the MIT license?
Temporal is Open Source with MIT license. Please refer to stackoverflow post for a more complete comparison between the two open source projects.
Cadence now supports gRPC communication with backward compatible upgrade story. https://cadenceworkflow.io/blog/2021/10/19/moving-to-grpc/
Currently Cadence defines frontend API as thrift and uses yarpc over tchannel for communication between external clients and Cadence service. This issue is to expose gRPC protocol head for the public API and define protobuff definitions for all public API. Initially this API implementation could just proxy API calls to thrift API handlers.