<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Resilience on Abdelbaki Ben Elhaj Slimene</title><link>https://bakic.github.io/tags/resilience/</link><description>Recent content in Resilience on Abdelbaki Ben Elhaj Slimene</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 20 Mar 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://bakic.github.io/tags/resilience/index.xml" rel="self" type="application/rss+xml"/><item><title>High availability VS Fault Tolerance VS Disaster Recovery</title><link>https://bakic.github.io/posts/high-availability-vs-fault-tolerance-vs-disaster-recovery/</link><pubDate>Mon, 20 Mar 2023 00:00:00 +0000</pubDate><guid>https://bakic.github.io/posts/high-availability-vs-fault-tolerance-vs-disaster-recovery/</guid><description>&lt;p&gt;High availability, Fault Tolerance and Disaster Recovery are three concepts to understand for every Solution Architect. These concepts are sometimes mixed and the difference between each one is not clear enough.&lt;/p&gt;&#10;&lt;h4 id="high-availability-ha"&gt;High Availability (HA)&lt;/h4&gt;&#10;&lt;p&gt;First, let&amp;rsquo;s try to give the definition of high availability. Wikipedia has a pretty good one:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;High availability&lt;/strong&gt; (&lt;strong&gt;HA&lt;/strong&gt;) is a characteristic of a system which aims to ensure an agreed level of operational performance, usually &lt;a href="https://en.wikipedia.org/wiki/Uptime"&gt;uptime&lt;/a&gt;, for a higher than normal period.&lt;/p&gt;&#10;&lt;/blockquote&gt;</description></item></channel></rss>