<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Design Patterns on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/categories/design-patterns/</link>
    <description>Recent content in Design Patterns on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 17 Dec 2024 12:00:10 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/categories/design-patterns/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why Being Proactive Is Always a Winning Approach</title>
      <link>https://ronaldbradford.com/blog/why-being-proactive-is-always-a-winning-approach-2024-12-17/</link>
      <pubDate>Tue, 17 Dec 2024 12:00:10 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/why-being-proactive-is-always-a-winning-approach-2024-12-17/</guid>
      <description>Many companies manage production infrastructure using a reactive model rather than a proactive one. Organizations typically react to warnings and alerts, then implement corrective actions in response. While some companies have well-designed architectural patterns—such as feature flags and rate limiting—that can quickly mitigate the impact of issues, these are merely temporary solutions, not resolutions.</description>
    </item>
  </channel>
</rss>
