
  <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, 01 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.rambling-me.com/tags/cap/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.rambling-me.com/blog/posts/technology/scaling/orders-of-magnitude/4-choosing-under-constraints</guid>
    <title>Scaling: Choosing Under Constraints</title>
    <link>https://www.rambling-me.com/blog/posts/technology/scaling/orders-of-magnitude/4-choosing-under-constraints</link>
    <description>How to actually decide which levers to pull. The forcing axes are consistency versus availability, cost, operational burden, and team maturity. CAP and PACELC give the tradeoff precise words, premature optimization is the default failure mode, and the domain you are in, banking versus commerce versus advertising, quietly decides which cost you refuse to pay.</description>
    <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    <author>me@rambling-me.com (Dopeking)</author>
    <category>technology</category><category>scaling</category><category>orders-of-magnitude</category><category>system-design</category><category>CAP</category><category>consistency</category><category>tradeoffs</category><category>practitioner</category>
  </item>

    </channel>
  </rss>
