<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Site Reliability on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/categories/site-reliability/</link>
    <description>Recent content in Site Reliability on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 06 Dec 2013 16:20:53 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/categories/site-reliability/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Simple steps to increasing site availability</title>
      <link>https://ronaldbradford.com/blog/simple-steps-to-increasing-site-availability-2013-12-06/</link>
      <pubDate>Fri, 06 Dec 2013 16:20:53 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/simple-steps-to-increasing-site-availability-2013-12-06/</guid>
      <description>A recent database production migration with a large client highlighted a fundamental flaw in their designed architecture for suitable site availability. While the development team had take several good steps in improving scalability of the site, there was a clear failure in understanding and supporting different levels of data availability which I cover in my presentation Successful Scalability Principles .</description>
    </item>
    <item>
      <title>Performance v Scalability – For Employers</title>
      <link>https://ronaldbradford.com/blog/performance-v-scalability-for-employers-2013-12-04/</link>
      <pubDate>Wed, 04 Dec 2013 23:20:18 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/performance-v-scalability-for-employers-2013-12-04/</guid>
      <description>In a recent discussion with a fellow peer reviewing a job description he was applying for, we got into a discussion on the specifics of a Performance Engineer verses a Scalability Engineer.</description>
    </item>
    <item>
      <title>Clearly define your uptime needs</title>
      <link>https://ronaldbradford.com/blog/clearly-define-your-uptime-needs-2013-12-03/</link>
      <pubDate>Tue, 03 Dec 2013 21:36:16 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/clearly-define-your-uptime-needs-2013-12-03/</guid>
      <description>In writing about Performance and Scalability I referenced a quote that I have provided in a number of presentations regarding a valuable interaction with a client. All software architects and managers need to clearly understand this for their own sites in order to enable technical resources to deliver a highly scalable solution.</description>
    </item>
  </channel>
</rss>
