<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Performance on System Design</title><link>https://system-design.devops-monk.com/tags/performance/</link><description>Recent content in Performance on System Design</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 30 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://system-design.devops-monk.com/tags/performance/index.xml" rel="self" type="application/rss+xml"/><item><title>Back-of-the-Envelope Estimation: The Art of Making Smart Guesses</title><link>https://system-design.devops-monk.com/2026/05/back-of-the-envelope-estimation/</link><pubDate>Sat, 30 May 2026 00:00:00 +0000</pubDate><guid>https://system-design.devops-monk.com/2026/05/back-of-the-envelope-estimation/</guid><description>Imagine your interviewer says: &amp;ldquo;We&amp;rsquo;re designing Instagram Stories. How much storage do we need per year?&amp;rdquo;
Most junior engineers freeze. They don&amp;rsquo;t know where to begin. They feel like they need exact numbers — the real database size, the real compression ratios, the real usage stats.
Here&amp;rsquo;s the secret: you are not supposed to be exact. You are supposed to be directionally correct.
Back-of-the-envelope estimation is the skill of producing a reasonable answer in 2–3 minutes using simple math and a handful of memorized numbers.</description></item></channel></rss>