Skip to main content
Software Engineering Daily

Orkes and Agentic Workflow Orchestration with Viren Baraiya

46 min episode · 2 min read
·
Viren Baraiya

Episode

46 min

Read time

2 min

Topics

Productivity, Remote Work, Artificial Intelligence

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?

Episode Transcript

Modern software systems are composed of many independent microservices spanning front ends, back ends, APIs, and AI models, and coordinating and scaling them reliably is a constant challenge. A workflow orchestration platform addresses this by providing a structured framework to define, execute, and monitor complex workflows with resilience and clarity. Orkas is an enterprise scale agentic orchestration platform that builds on the open source Conductor project, which was pioneered at Netflix. The platform coordinates AI agents, humans, and APIs with a focus on scalability, compliance, and trust. It further expands on the Conductor core by adding features like security, governance, and long running workflows. Viran Bareya is the founder and CTO at orcas, and he's the creator of Netflix Conductor. Vran joins the show with Gregor Vann to talk about his building Conductor at Netflix, the challenge of orchestrating microservices, rule based versus programmatic workflow orchestration, agentic orchestration, MCP integration, and much more. Gregor Vand is a security focused technologist, having previously been a CTO across cybersecurity, cyber insurance, and general software engineering companies. He is based in Singapore and can be found via his profile at van.hk or on LinkedIn. Hello and welcome to Software Engineering Daily. My guest today is Verein Barreya from Arcus. So we're gonna be talking all about what Arcus does and especially Arcus Conductor and some of you may already know the word conductor from some other companies and we're gonna be talking about that. But, yeah, welcome, Bahrain. Thanks, Gregor, for having me here and I'm very excited to be here. Yeah. So as we do on this podcast tradition, we just like to kind of get an understanding of your background. You've definitely worked at quite a few interesting companies that I think our audience will be fairly familiar with. But, yeah, just walk us through what's your kind of career path, I guess, to orcas. Yeah. I started orcas about close to getting four years now. And prior to orcas, I spent, like, in very different set of industries. Right? So before orcas, I spent almost few years at Google mostly working on developer products, so Firebase and Google Play. This is one a place where I got to kind of work with, you know, developer as one of the audiences. How do they interact with systems and how do you build for them? Which was also kind of one of the reasons why, you know, which kind of motivated me to build orcas. More interestingly, before Google, I spent my time at Netflix, which is where I was part of an infrastructure team that was responsible for building the platform for Netflix's back then very ambitious, you know, studio project. Right? Basically, the goal was to build the largest production studio in the world and to enable that. There is, of course, the whole production side, but at the same time, there was the engineering side in terms of building out the products and tools. And my team was responsible …

Get the full transcript (9,522 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all Software Engineering Daily transcripts →

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

Books, tools, and gear mentioned in this episode

SignalCast may earn commission on purchases via these links.

Tools

  • OrkesBy guest

    by Orkes

    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.
  • by Netflix

    Viren Baraiya explains how Orkes builds on Netflix Conductor to orchestrate microservices, APIs, and AI agents at enterprise scale

More from Software Engineering Daily

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

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

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

Read this week's AI & Machine Learning Podcast Insights — cross-podcast analysis updated weekly.

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 one show.

Start My Monday Digest

No credit card · Unsubscribe anytime