What features could Temporal add to its distributed cron functionality to make scheduling more flexible for users?

Introduction

Temporal's distributed cron functionality is a powerful tool for scheduling tasks in distributed systems. To enhance its flexibility for users, we need to explore potential features that could address current limitations and provide more granular control over scheduling. I'll approach this challenge by first understanding the current product context, identifying key user segments, analyzing pain points, and then proposing and evaluating solutions.

Step 1

Clarifying Questions (5 mins)

• Looking at Temporal's distributed cron functionality, I'm thinking it might be primarily used by DevOps engineers and system administrators. Could you help me understand who the primary users are and what their main use cases for this feature are?

Why it matters: Determines the focus of our improvements and ensures we're solving the right problems. Expected answer: DevOps engineers and SREs managing large-scale distributed systems. Impact on approach: Would tailor solutions to technical users' needs vs. general developers.

• Considering the evolving landscape of cloud-native applications, I'm curious about how users are currently interacting with Temporal's cron functionality. Are they primarily using it through a CLI, API, or some form of UI?

Why it matters: Influences the type of improvements we might propose (e.g., UI enhancements vs. API extensions). Expected answer: Primarily through API and CLI, with some basic UI integration. Impact on approach: Would focus on programmatic improvements and CLI enhancements.

• Given that flexibility is a key concern, I'm wondering about the current limitations users are facing. What are the most common feature requests or complaints about the current cron functionality?

Why it matters: Directly informs the pain points we need to address. Expected answer: Limited support for complex schedules, lack of timezone handling, no easy way to manage dependencies between jobs. Impact on approach: Would prioritize features that address these specific limitations.

• Considering Temporal's position in the market, I'm interested in understanding how this improvement aligns with the company's broader strategy. Are we looking to differentiate from competitors, or is this more about meeting specific customer demands?

Why it matters: Helps align our proposed solutions with Temporal's overall product strategy. Expected answer: Both - meeting customer demands while maintaining a competitive edge in the workflow orchestration space. Impact on approach: Would balance innovative features with practical, high-demand improvements.