<?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>vertical-scaling on Eric&#39;s Note</title>
    <link>https://eric.nz/tags/vertical-scaling/</link>
    <description>Recent content in vertical-scaling on Eric&#39;s Note</description>
    <image>
      <url>https://eric.nz/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://eric.nz/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Mon, 06 Mar 2017 16:12:41 +0000</lastBuildDate><atom:link href="https://eric.nz/tags/vertical-scaling/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>System Design - Vertical and Horizontal Scaling</title>
      <link>https://eric.nz/posts/sys-design-iv-vertical-horizontal-scaling/</link>
      <pubDate>Mon, 06 Mar 2017 16:12:41 +0000</pubDate>
      
      <guid>https://eric.nz/posts/sys-design-iv-vertical-horizontal-scaling/</guid>
      <description>There are two common ways to scale your application: Vertical Scaling and Horizontal Scaling .
Let&amp;rsquo;s say you have your own web app and it&amp;rsquo;s running on a single server to start, the number of users rapidly growing, and you may start to meet some performance bottleneck in following aspect:
CPU. If you are doing a certain function that requires a lot of processing power, like image conversion or video decoding.</description>
    </item>
    
  </channel>
</rss>
