<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Microservices on christos gkoros</title>
    <link>https://christosgkoros.com/tags/microservices/</link>
    <description>Recent content in Microservices on christos gkoros</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 15 May 2026 08:00:00 +0300</lastBuildDate>
    <atom:link href="https://christosgkoros.com/tags/microservices/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Agents Are the New Microservices</title>
      <link>https://christosgkoros.com/posts/2026/05/15/agents-are-the-new-microservices/</link>
      <pubDate>Fri, 15 May 2026 08:00:00 +0300</pubDate>
      <guid>https://christosgkoros.com/posts/2026/05/15/agents-are-the-new-microservices/</guid>
      <description>1. Single responsibility works best People tend to model agents on people: a product owner agent, an engineer agent, a QA agent. That fails for the same reason UserService failed. A role is not a scope. It is a bundle of unrelated jobs that share a title.&#xA;Single-task agents hold up better. A backlog grooming agent. A release notes agent. A migration risk review agent. One job you can describe in a sentence, with a small tool surface and a clear output.</description>
    </item>
  </channel>
</rss>
