
  <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>Tue, 25 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.rambling-me.com/tags/resilience/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.rambling-me.com/blog/posts/technology/scaling/ui-frontend/4-client-resilience</guid>
    <title>Scaling the UI: Client Resilience and the Cross-Cut</title>
    <link>https://www.rambling-me.com/blog/posts/technology/scaling/ui-frontend/4-client-resilience</link>
    <description>Closing the frontend track and the pillar. The client faces the same scale and failure the backend does, and has to stay trustworthy through it: graceful degradation, retry with backoff, offline and flaky-network handling. Then the cross-cut that ties the pillar together, auth that scales, client-side rate limiting, and frontend observability that closes the loop back to knowing your numbers. Plus the native reality of un-hot-fixable clients.</description>
    <pubDate>Tue, 25 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>resilience</category><category>offline</category><category>authentication</category><category>observability</category><category>practitioner</category>
  </item>

    </channel>
  </rss>
