Maxim Fateev

@asmah2107 We at @temporalio see a lot of orchestrated agents. This doesn’t preclude peer to peer communication when needed.

The most underrated architecture decision in multi-agent systems: Orchestrated (one boss agent delegates) vs. Choreographed (agents negotiate peer-to-peer) Microservices solved this in 2015. Nobody ported the answer to agents yet. The trade-offs are identical. The stakes are higher.

Temporal CEO Samar Abbas: “A couple of years ago actually, I said: looks like we have over-engineered on scale. What's the use case where we need this much scale? And then of course, the whole AI agent wave happened." Sometimes you build the right thing too early. Great pod with @SamarAtTemporal:

This was so much fun. Thanks @sarahdingwang @RaghuRaghuram for having me.

When we asked leading AI companies what they were using as foundational infrastructure, one name kept popping up over and over again. It is the same one that has been powering mission-critical workflows for large enterprises and digital natives. @temporalio Temporal is building the execution layer to power workflows at scale reliably, an undeniable need as agents move from experiments to production. As leading minds that have been pushing the frontier in this space for over a decade, there are no two people better in the world to tackle this problem than @SamaratTemporal and @mfateev, and we @a16z are excited to lead their Series D. More from our team: a16z.com/announcement/i…

Long-running systems shouldn’t require constant rework to stay secure. This is why, when services run for years, it’s essential that security be built into the foundation - not bolted on later. @temporalio CTO @mfateev on how free Docker Hardened Images and Extended Lifecycle Support make that possible:

AI is powerful, but it needs us. After spending time vibe coding, it's clear that we are in an industrial revolution for software development. Your career isn't ending. It's evolving. Here's what that actually means → temporal.io/blog/what-will…

@nicoup @corbtt @temporalio Send me an email at my first name at temporal.io, and we'll arrange a meeting.

@mfateev @corbtt @temporalio happy to!

I'm bullish on @temporalio. Their abstractions are strong in general but are a particularly good match for long-running background agents.

@nicoup @corbtt @temporalio What about meeting with our design and UI teams to give specific feedback?

@corbtt @temporalio Imagine if temporal had better ui. Would be unstoppable

@leilavclark With Temporal you write your code as failure doesn’t exist. This eliminates majority of boilerplate code. It works for any use case from infra automation to agentic loops that needs guarantee of completion.

can someone explain to me what temporal is and what it does, without using the words “durable execution”?

"System Design Series: A Step-by-Step Breakdown of Temporal’s Internal Architecture" by Sanil Khurana medium.com/data-science-c…

When comparing durable execution trees to queues, it is important to realize that the functions can belong to different services. To me, it sounds like you imply that having services without any APIs (which is EDA) is better than well-defined API boundaries. Another misconception is that EDA systems are loosely coupled. They are not, as any event format change can break an unknown number of consumers. Events are global variables of distributed systems.

New blog post: The Durable Function Tree (part 1 and 2) I’ve been looking at how durable execution engines actually organise work. Underneath all the abstractions, most of them end up building some form of durable function tree: functions calling functions, each returning a durable promise, with the engine suspending and resuming work through replay and memoization. There is also a key distinction between local-context side effects (synchronous, can’t suspend) and remote-context side effects (durable functions, timers, delegation), which define where suspension points exist. Different frameworks expose the tree in different ways, and also constrain the tree's structure: Temporal and DBOS constrains the tree to two levels (workflow → activities/step), whereas others such as Restate and Resonate allow arbitrary depth. In the end, we can obtain reliable multi-step workflows without durable execution. I tackle the question of what the true value-add is of durable execution, its limits and how it should be combined with other approaches like event-driven architecture. Full post: jack-vanlightly.com/blog/2025/12/4…

New blog post: Demystifying Determinism in Durable Execution A topic that confuses many when they start using durable execution frameworks like Temporal, Restate, DBOS, or Resonate is determinism. Why do some parts of a durable function have to be deterministic while others idempotent or tolerant of duplication? In this post, I explain a simple mental model that generalizes the framework-specific terminology (“workflows”, “activities”, “handlers”, “durable steps”) into a set of underlying mechanics relevant to determinism: 🔹 Why durable execution relies on re-executing functions 🔹 How control flow and side effects play different roles 🔹 Where and why determinism is needed vs idempotency Post: jack-vanlightly.com/blog/2025/11/2…

@tylerangert +Durable Execution (workflows) like @temporalio

all personal software apps will eventually converge on building the same foundational infra: - a sandboxed FS (virtual or real, depending on if you need a vm) - a coding agent that knows how to create / edit / remove files - a react runtime (e.g. dev server of some kind, renderer, custom globals + libraries) - a builtin backend that makes it easy for the coding agent to persist data (in memory, supabase, on disk, etc) im also bearish on any coding agents creating "native apps" longterm especially with the new mini apps program unless apple somehow opens up a swift interpreter / sandboxed swift execution. this all belongs to web. i do think that there may be an open source company focused on packaging a lot of this up - if not the entire thing, at least the "coding agent in a box". claude agents sdk is close but it's missing a lot of the opionated setup needed to quickly go from prompt -> compiled JS you can run in any browser.

Temporal is a finalist in the 2025 DevOps Dozen Awards 🎉 If we've ever made your systems more reliable, reduced your on-call stress, or simply intro'd you to the best animal ever (hello, tardigrade), please vote for us ➡️ surveymonkey.com/r/DevOps-Dozen…

The Temporal Swift SDK lets you write reliable, long-running Workflows with Swift’s native async/await and structured concurrency. Details + docs → temporal.io/blog/temporal-…

@KentonVarda That wasn’t our experience at @temporalio. Having fully functional MIT Licensed OSS is enough for companies to not fear the paid service.

"Hey folks I made a new tech! It's faster, cheaper, easier, and just fundamentally better than what you use today!" "NOOOOOOOOO you are trying to LOCK US IN! This is clearly an evil plot!" "OK I made it open source, you can run it on your own infra." "NOOOO STILL EVIL!" 🤷

Just announced - the new Temporal Swift SDK! Try it out at github.com/apple/swift-te…"

Managing long-running, stateful workflows in Swift just got a whole lot easier. The new Temporal SDK brings first-class support for building reliable, fault-tolerant applications. swift.org/blog/swift-tem… @temporalio