Temporal's integrated gRPC support and our shared proto definitions

Community Support
1

We have numerous microservices (mostly GO some Java) exclusively using gRPC to communicate with one another and the front end via GraphQL. Hence, there are a significant number of protos defined and shared among the microservices in a monorepo. How do we expose/use our protos in a Temporal solution using it’s integrated gRPC support?

We are looking at Temporal to help mitigate some of the negative issues with eventing and long running processes that can fail.

2

Temporal supports proto objects as payloads (workflow and activity inputs and results, signal payloads, etc) out of the box.

1 Like
3

Thanks for the quick response.