<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud on I am Lino</title><link>https://iamlino.net/en/tags/cloud/</link><description>Recent content in Cloud on I am Lino</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 16 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://iamlino.net/en/tags/cloud/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Make Technical Decisions Without Selling Your Soul to the Hype</title><link>https://iamlino.net/en/blog/how-to-make-technical-decisions-without-selling-your-soul-to-the-hype/</link><pubDate>Mon, 16 Mar 2026 00:00:00 +0000</pubDate><guid>https://iamlino.net/en/blog/how-to-make-technical-decisions-without-selling-your-soul-to-the-hype/</guid><description>&lt;p&gt;There are technical decisions made with data, time, and a bit of judgment.&lt;/p&gt;
&lt;p&gt;And then there are the other kind: the ones made after watching three conference talks, scrolling through two X threads, and half-reading a &lt;a href="https://garden.io/blog/seven-hard-earned-lessons-learned-migrating-a-monolith-to-microservices" target="_blank" rel="noopener"&gt;case study&lt;/a&gt;
, that somehow end with phrases like &amp;ldquo;well&amp;hellip; now that we&amp;rsquo;ve set it all up, we might as well get some use out of it, right?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;One day you&amp;rsquo;re perfectly happy with your API running on a plain old VPS, and the next you find yourself building a &lt;strong&gt;serverless-event-driven-data-mesh-multi-cloud&lt;/strong&gt; architecture because you watched a video claiming &amp;ldquo;that&amp;rsquo;s how Netflix does it.&amp;rdquo;&lt;/p&gt;</description></item><item><title>Modern Architecture Fundamentals (No Snake Oil Included)</title><link>https://iamlino.net/en/blog/modern-architecture-fundamentals-no-snake-oil-included/</link><pubDate>Mon, 02 Mar 2026 00:00:00 +0000</pubDate><guid>https://iamlino.net/en/blog/modern-architecture-fundamentals-no-snake-oil-included/</guid><description>&lt;p&gt;Imagine someone telling you: &amp;ldquo;I&amp;rsquo;ve set up my app on an on-premises server with Oracle 9i, but don&amp;rsquo;t worry, it&amp;rsquo;s modern architecture because it runs Docker.&amp;rdquo; That&amp;rsquo;s the moment you understand why people bail on architecture meetings pretending they have a dental emergency.&lt;/p&gt;
&lt;p&gt;When we talk about &lt;strong&gt;&amp;ldquo;modern architecture,&amp;rdquo;&lt;/strong&gt; we&amp;rsquo;re not talking about slapping Kubernetes onto everything or cramming as many buzzwords as possible into a slide deck. We&amp;rsquo;re talking about something far less flashy and far more difficult: building systems that survive in &lt;a href="https://apptastic-coder.com/tutorials/2025-11-3-architecture-comparison/" target="_blank" rel="noopener"&gt;today&amp;rsquo;s ecosystem&lt;/a&gt;
 without going obsolete or blowing up every time the business changes a &amp;ldquo;simple&amp;rdquo; requirement. Systems that live in the cloud (or several clouds), communicate over networks that fail, store data scattered across half the planet, and still need to keep responding when someone decides &amp;ldquo;we also need to go multi-region because an important client said so.&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>