<?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>Distributed-Systems on Gökmen Görgen</title><link>https://gokmengorgen.net/tags/distributed-systems/</link><description>Recent content in Distributed-Systems on Gökmen Görgen</description><generator>Hugo -- 0.150.0</generator><language>en</language><copyright>Content licensed under the Creative Commons attribution-noncommercial-sharealike License.
Please look at this url for more information.</copyright><lastBuildDate>Sat, 27 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://gokmengorgen.net/tags/distributed-systems/index.xml" rel="self" type="application/rss+xml"/><item><title>Cloud Design Patterns: A Practical Tour</title><link>https://gokmengorgen.net/2026/06/27/cloud-design-patterns-a-practical-tour/</link><pubDate>Sat, 27 Jun 2026 00:00:00 +0000</pubDate><guid>https://gokmengorgen.net/2026/06/27/cloud-design-patterns-a-practical-tour/</guid><description>&lt;p&gt;Maybe you&amp;rsquo;ve had a different experience, but I&amp;rsquo;ve never once looked at a system and said, &amp;ldquo;This is perfect, we&amp;rsquo;re done here.&amp;rdquo; There is always a new requirement, a shifting bottleneck, or a sudden spike in traffic. You can&amp;rsquo;t build a distributed system without at least one of your services eventually collapsing under the weight of its own dependencies. It&amp;rsquo;s a rite of passage. This is a tour of the patterns I keep reaching for across backend systems — written for engineers new to distributed architecture. We&amp;rsquo;ll start with the one that usually forces you to learn about all the others.&lt;/p&gt;</description></item></channel></rss>