<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Architecture Patterns on No Semicolons</title><link>https://nosemicolons.com/tags/ai-architecture-patterns/</link><description>Recent content in AI Architecture Patterns on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 27 Jun 2026 09:57:23 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/ai-architecture-patterns/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Microservice Maze: How to Build Distributed Systems When Your AI Only Thinks Monolith</title><link>https://nosemicolons.com/posts/ai-code-generation-microservice-maze-distributed-systems/</link><pubDate>Sat, 27 Jun 2026 09:57:23 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-microservice-maze-distributed-systems/</guid><description>&lt;p>Ever asked Claude or GPT to help you build a microservices architecture, only to get back a beautifully crafted&amp;hellip; monolith? You&amp;rsquo;re not alone. I&amp;rsquo;ve been down this rabbit hole more times than I care to admit, watching AI assistants confidently generate single services that somehow manage users, payments, notifications, and probably make coffee too.&lt;/p>
&lt;p>The thing is, our AI coding companions are incredible at understanding individual components, but they often miss the forest for the trees when it comes to distributed system design. They default to what they know best: clean, cohesive code blocks that live happily in one place.&lt;/p></description></item></channel></rss>