<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Software Architecture on Diego Rodrigo</title><link>https://diegorodrigo.dev/en/series/software-architecture/</link><description>Recent content in Software Architecture on Diego Rodrigo</description><image><title>Diego Rodrigo</title><url>https://diegorodrigo.dev/blog-image.png</url><link>https://diegorodrigo.dev/blog-image.png</link></image><generator>Hugo</generator><language>en</language><copyright>Copyright © 2022 - Diego Rodrigo. All rights reserved.</copyright><lastBuildDate>Tue, 14 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://diegorodrigo.dev/en/series/software-architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>System design without theater: what really changes when a system needs to scale</title><link>https://diegorodrigo.dev/en/2026/04/14/system-design-without-theater-what-really-changes-when-a-system-needs-to-scale/</link><pubDate>Tue, 14 Apr 2026 00:00:00 -0300</pubDate><guid>https://diegorodrigo.dev/en/2026/04/14/system-design-without-theater-what-really-changes-when-a-system-needs-to-scale/</guid><description>A practical look at what usually changes first when a system starts growing: separation of responsibilities, replicas, caching, queues, and the trade-offs that show up early.</description></item></channel></rss>