How can Temporal improve its workflow versioning capabilities to better support complex application upgrades?

Introduction

Temporal's workflow versioning capabilities are crucial for supporting complex application upgrades. To improve this feature, we need to understand the current pain points, user needs, and potential solutions that align with Temporal's overall product strategy. I'll analyze the problem, propose solutions, and outline a roadmap for implementation.

Step 1

Clarifying Questions (5 mins)

• Looking at Temporal's position in the workflow orchestration market, I'm curious about the specific types of applications and industries that are driving the need for improved versioning capabilities. Could you share some insights on the primary use cases and industries where Temporal is seeing the most traction, particularly where complex upgrades are a challenge?

Why it matters: This helps us tailor the versioning improvements to the most critical user needs and use cases. Expected answer: Microservices architectures in fintech and e-commerce are driving complex upgrade scenarios. Impact on approach: Would focus on features supporting gradual rollouts and backwards compatibility for financial transactions.

• Considering the evolving nature of distributed systems, I'm wondering about the current limitations of Temporal's versioning capabilities. What are the most common versioning-related issues or feature requests reported by users when dealing with complex application upgrades?

Why it matters: Identifies specific pain points to address in our solution. Expected answer: Users struggle with managing multiple workflow versions in production and handling schema changes. Impact on approach: Would prioritize features for side-by-side version running and automated schema migration tools.

• Given the critical nature of workflow orchestration in production environments, I'm interested in understanding the risk tolerance of Temporal's user base. How do users typically approach testing and rolling out new versions of their workflows, and what safety mechanisms are they looking for?

Why it matters: Helps balance innovation with stability in our versioning solution. Expected answer: Users prefer gradual rollouts with easy rollback options and extensive monitoring. Impact on approach: Would focus on developing robust canary deployment features and enhanced observability for version transitions.

• Considering Temporal's open-source nature and ecosystem, I'm curious about the level of customization and extensibility users expect in versioning solutions. How important is it for users to be able to integrate their own versioning strategies or tools with Temporal's capabilities?

Why it matters: Determines the balance between out-of-the-box solutions and extensibility in our approach. Expected answer: Users value flexibility but also want strong defaults and best practices built-in. Impact on approach: Would design a modular versioning system with clear extension points and comprehensive documentation.