{
  "id": 1933291,
  "title": "What the Microservices Era Can Teach Us About AI",
  "url": "https://urgent.news/2026/08/19/what-the-microservices-era-can-teach-us-about-ai",
  "topic": "ai",
  "section": "AI",
  "published": "2026-08-19T12:01:07.000Z",
  "source": {
    "name": "DevOps.com",
    "slug": "devops-com",
    "url": "https://devops.com/what-the-microservices-era-can-teach-us-about-ai/"
  },
  "original_language": "en",
  "account": "The most common mistake teams make with AI agents is treating them as microservices with a language model added on. Microservices are a familiar architecture for platform engineers, and agents seem like services that happen to think. But this analogy breaks down quickly. Microservices changed software development by allowing teams to work independently, ship faster, and scale efficiently. However, agents require a different approach. They can run for hours or days, touch multiple systems, and make non-deterministic decisions that go unnoticed until much later. This is where the microservices playbook both applies and doesn't, and why treating agents as just distributed services is a trap. The lessons learned from the microservices era need to be rewritten for the agent era. First, durable execution stops being a pattern and becomes the runtime. In a deterministic world, you can add resilience later, but in the agent era, resilience must be part of the runtime from the start. Second, security and governance need a new model. Microservices pushed authentication to the edge, but agents can start other agents at runtime, creating new questions about permissions and traceability. The solution is not just stronger boundaries, but a series of locked doors with individual credentials and cryptographic attestation for every step of every workflow. Third, observability has to reach every step, not just the endpoint. Operators need to see exactly where a failure occurred in a long-running workflow, not just that it failed. This requires full visibility into every step an agent takes, creating a new capability called agentic durable execution. This guarantees recovery, carries autonomous AI agents and deterministic workflows to completion, and provides cryptographic evidence of what happened.",
  "summary": "AI agents are not just microservices with LLMs attached. Their long-running, non-deterministic workflows demand durable execution, per-step identity, governance and observability.",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}