<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cloud&#39;s Faults on DevopsTrain</title>
    <link>https://devopstrain.lifeisfile.com/tags/clouds-faults/</link>
    <description>Recent content in Cloud&#39;s Faults on DevopsTrain</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>©, Alex Babochkin</copyright>
    <lastBuildDate>Mon, 21 Oct 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://devopstrain.lifeisfile.com/tags/clouds-faults/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cloud infrastructure outages. Who&#39;s to blame?</title>
      <link>https://devopstrain.lifeisfile.com/post/clound-infr/</link>
      <pubDate>Mon, 21 Oct 2024 00:00:00 +0000</pubDate>
      
      <guid>https://devopstrain.lifeisfile.com/post/clound-infr/</guid>
      <description>
        
          
            A recent (yet another) outage in Yandex.Cloud nudged me toward this topic, in which we&#39;ll try to define the areas of responsibility and ways to protect yourself.
🧨 Incidents happen, whether it&#39;s a cloud or a server in a data center. Anything can happen: fire, flood, a drone strike, malicious actions, and so on. As the folk wisdom goes: There is no cloud, it is just someone&#39;s else computer.
But when choosing cloud solutions, we want to delegate responsibility for failures to the cloud service provider.
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
