BlogsTemporalPolyglot Workflows

Polyglot Workflows

Polyglot Workflows

1
posts
2024

Temporal Workflows can now be orchestrated across multiple programming languages. While a single Workflow definition must reside in one language, it can invoke Activities written in different languages. This requires separate Workers for each language and distinct task queue names to ensure proper routing. The Temporal SDKs handle automatic data type conversion between languages, enabling seamless interoperability. Example applications like Temporal Polyglot and Temporal Pendulum demonstrate this capability, showcasing how a primary language can orchestrate activities written in others.

2024

Community threads: Is it possible to write a single Workflow with different languages?

3/5/2024

This post introduces the concept and implementation details of using multiple programming languages within a single Temporal workflow. It explains that while a Workflow definition itself is language-specific, it can invoke Activities written in other languages. Key technical aspects covered include the need for separate Workers per language, unique task queue naming conventions to differentiate activities, and the automatic data type conversion provided by Temporal SDKs for cross-language interoperability. It also references example applications (Temporal Polyglot and Temporal Pendulum) that demonstrate this polyglot capability.