<?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 Yonatan Karp-Rudin</title><link>https://yonatankarp.com/tags/system-design/</link><description>Recent content in System Design on Yonatan Karp-Rudin</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 23 Oct 2023 00:00:00 +0100</lastBuildDate><atom:link href="https://yonatankarp.com/tags/system-design/index.xml" rel="self" type="application/rss+xml"/><item><title>Our Errors, Your Gain: A System Design Cautionary Tale</title><link>https://yonatankarp.com/blog/our-errors-your-gain-a-system-design-cautionary-tale/</link><pubDate>Mon, 23 Oct 2023 00:00:00 +0100</pubDate><guid>https://yonatankarp.com/blog/our-errors-your-gain-a-system-design-cautionary-tale/</guid><description>&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; This article shares my experience with a temporary solution that turned into a long-term issue. I discuss the evolution of a service and how it improved its performance by over 450% in a few hours. The story highlights the importance of addressing temporary solutions and constantly evaluating system design to optimize performance.&lt;/p&gt;&#10;&lt;/blockquote&gt;</description></item></channel></rss>