
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Rambling Me</title>
      <link>https://www.rambling-me.com/blog</link>
      <description>A blog to reflect my thoughts, learnings, and observations</description>
      <language>en-us</language>
      <managingEditor>me@rambling-me.com (Dopeking)</managingEditor>
      <webMaster>me@rambling-me.com (Dopeking)</webMaster>
      <lastBuildDate>Sat, 15 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.rambling-me.com/tags/cdn/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.rambling-me.com/blog/posts/technology/scaling/ui-frontend/1-bytes-to-the-client-cheaply</guid>
    <title>Scaling the UI: Getting Bytes to the Client Cheaply</title>
    <link>https://www.rambling-me.com/blog/posts/technology/scaling/ui-frontend/1-bytes-to-the-client-cheaply</link>
    <description>The frontend track opens on the read path. The cheapest request your backend ever handles is the one it never receives, so scaling the client is largely about serving bytes from as far out as possible: CDNs and the edge, HTTP and client caching, right-sized payloads, and pagination. Plus the native-app angle, where on-device storage becomes a real cache tier.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>me@rambling-me.com (Dopeking)</author>
    <category>technology</category><category>scaling</category><category>ui-frontend</category><category>cdn</category><category>caching</category><category>pagination</category><category>payload</category><category>practitioner</category>
  </item>

    </channel>
  </rss>
