Skip to main content
Software Engineering Daily

Orkes and Agentic Workflow Orchestration with Viren Baraiya

46 min episode · 2 min read
·

Episode

46 min

Read time

2 min

AI-Generated Summary

Key Takeaways

  • Programmatic orchestration advantage: Conductor uses code-like workflow definitions instead of rule-based systems, allowing developers to write workflows exactly as they think about code with loops, parallel execution, and decision cases, eliminating translation friction between business rules and implementation.
  • Synchronous microservices orchestration: Orkes extends traditional asynchronous workflow engines to support both extremely long-running workflows lasting months or years and ultra-low-latency synchronous orchestration completing entire flows in tens of milliseconds for true real-time service coordination.
  • Agentic guardrails implementation: Developers explicitly define which tool executions require human approval rather than letting LLMs decide when to apply guardrails, preventing autonomous agents from executing destructive operations like cluster deletion without verification while allowing safe read operations to proceed.
  • Multi-agent tool composition: Instead of building deterministic workflows for every use case, developers create stateless tools that LLMs combine dynamically, shifting from linear development of specific paths to combinatorial possibilities where agents select appropriate tool sequences based on context.

What It Covers

Viren Baraiya explains how Orkes builds on Netflix Conductor to orchestrate microservices, APIs, and AI agents at enterprise scale, focusing on programmatic workflows, long-running processes, guardrails, and trust mechanisms for agentic systems.

Key Questions Answered

  • Programmatic orchestration advantage: Conductor uses code-like workflow definitions instead of rule-based systems, allowing developers to write workflows exactly as they think about code with loops, parallel execution, and decision cases, eliminating translation friction between business rules and implementation.
  • Synchronous microservices orchestration: Orkes extends traditional asynchronous workflow engines to support both extremely long-running workflows lasting months or years and ultra-low-latency synchronous orchestration completing entire flows in tens of milliseconds for true real-time service coordination.
  • Agentic guardrails implementation: Developers explicitly define which tool executions require human approval rather than letting LLMs decide when to apply guardrails, preventing autonomous agents from executing destructive operations like cluster deletion without verification while allowing safe read operations to proceed.
  • Multi-agent tool composition: Instead of building deterministic workflows for every use case, developers create stateless tools that LLMs combine dynamically, shifting from linear development of specific paths to combinatorial possibilities where agents select appropriate tool sequences based on context.

Notable Moment

Baraiya reveals that Orkes became a larger contributor to Conductor than Netflix itself while the project was still in Netflix's repository, leading to the decision to transfer ownership and accelerate development velocity under dedicated commercial stewardship.

Know someone who'd find this useful?

You just read a 3-minute summary of a 43-minute episode.

Get Software Engineering Daily summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

More from Software Engineering Daily

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.

You're clearly into Software Engineering Daily.

Every Monday, we deliver AI summaries of the latest episodes from Software Engineering Daily and 192+ other podcasts. Free for up to 3 shows.

Start My Monday Digest

No credit card · Unsubscribe anytime