<?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>Architecture on VictorNM</title><link>https://victornm.github.io/tags/architecture/</link><description>Recent content in Architecture on VictorNM</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 04 Apr 2026 10:00:00 +0700</lastBuildDate><atom:link href="https://victornm.github.io/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Quality Attributes: The Architecture Decisions Nobody Writes Down</title><link>https://victornm.github.io/posts/system-quality-attributes/</link><pubDate>Sat, 04 Apr 2026 10:00:00 +0700</pubDate><guid>https://victornm.github.io/posts/system-quality-attributes/</guid><description>&lt;p>You can specify &amp;ldquo;99.9% availability&amp;rdquo; and &amp;ldquo;&amp;lt; 200ms latency&amp;rdquo; perfectly in a requirements doc. But a spec doesn&amp;rsquo;t tell you &lt;em>how&lt;/em> to build it, or what you&amp;rsquo;ll sacrifice to get there.&lt;/p></description></item></channel></rss>