Could temporal interface be language netural?


I am wondering if temporal interface can be something like thrift or protobuff which are totally language netural. This can make the following easier :

  • SDKs of different languages can communicate easily using this IDL + code generation.
  • Generic activity or workflow calls can be easier based on the netural encoding and decoing protocal.

It is very common for users to use protocol buffer based input/output for activities and workflows across languages. All SDKs support them. Granted they’d just use string names to pick which workflow/activity.

Some users have written code generators from common IDLs for their personal use, but Temporal does not (yet) have a blessed version of this.

1 Like