<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>System Design on I am Lino</title><link>https://iamlino.net/en/tags/system-design/</link><description>Recent content in System Design on I am Lino</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 09 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://iamlino.net/en/tags/system-design/index.xml" rel="self" type="application/rss+xml"/><item><title>Microservices, Monoliths, and Other Mythical Creatures</title><link>https://iamlino.net/en/blog/microservices-monoliths-mythical-creatures/</link><pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate><guid>https://iamlino.net/en/blog/microservices-monoliths-mythical-creatures/</guid><description>&lt;p&gt;Some architecture decisions are made calmly, with data, over a nice cup of coffee.&lt;/p&gt;
&lt;p&gt;And then there&amp;rsquo;s real life, where you pick your tech stack the same way you pick a favorite sports team: because you saw it in a cool conference talk, because some big-name company uses it, or because someone tweeted that &amp;ldquo;if you don&amp;rsquo;t have 80 microservices running on Kubernetes, you&amp;rsquo;re a dinosaur.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Next thing you know, you&amp;rsquo;ve gone from a lovable monolith — a little messy but functional — to a circus of services where nobody really knows what talks to what, your cloud bill is terrifying, and the only microservice running flawlessly is the one that charges you at the end of the month. All because, at some point, somebody stopped asking the only question that actually matters:&lt;/p&gt;</description></item></channel></rss>