---
title: "Discussion on \"AI Agents Are Distributed Systems. We Just Gave the Problem a New Name.\" | Hashnode"
description: "Discussion on \"AI Agents Are Distributed Systems. We Just Gave the Problem a New Name.\". The complete map between two worlds — the years, the receipts, and what building for it actually looks like."
url: "https://hashnode.com/posts/ai-agents-are-distributed-systems/6a53c8fb489799a821294947"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [AI Agents Are Distributed Systems. We Just Gave the Problem a New Name.](https://ravilanka.hashnode.dev/ai-agents-are-distributed-systems?utm_source=hashnode&utm_medium=feed)

The complete map between two worlds — the years, the receipts, and what building for it actually looks like.

Jul 12 · 9 min read · ravilanka.hashnode.dev  
Read the article

-   [#ai-agents](https://hashnode.com/tag/ai-agents)
-   [#distributed-systems](https://hashnode.com/tag/distributed-systems)
-   [#software-architecture](https://hashnode.com/tag/software-architecture)
-   [#llm](https://hashnode.com/tag/llm)
-   [#durableexecution](https://hashnode.com/tag/durableexecution)
-   [#ai](https://hashnode.com/tag/ai)

## Written by

[Ravi Lanka](https://hashnode.com/@ravilanka)

@ravilanka

  
[View profile](https://hashnode.com/@ravilanka)

Senior Software Engineer | Distributed Systems | Functional Programming Expert

## Responses 1

Markdown supported · ⌘↵ to post

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Jul 13](https://hashnode.com/posts/ai-agents-are-distributed-systems/6a53c8fb489799a821294947/comment/6a55336ef90af637f0354d4e)

The mapping holds, and the model-is-10%, harness-is-90% number is the part teams underweight when they pick a framework. The one that bites earliest for me is idempotency, people who'd never ship a service without idempotency keys will happily let an agent retry a non-idempotent tool call, then debug the double-executed action. If agent memory really is an event log, do you key tool-call results by an idempotency token so a retry replays instead of re-executes?
