<?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 Head for the Cloud</title>
    <link>https://headforthe.cloud/tags/resilience/</link>
    <description>Recent content in Resilience on Head for the Cloud</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 24 Dec 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://headforthe.cloud/tags/resilience/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Chaos in the Cloud</title>
      <link>https://headforthe.cloud/article/chaos-in-the-cloud/</link>
      <pubDate>Tue, 24 Dec 2024 00:00:00 +0000</pubDate>
      <guid>https://headforthe.cloud/article/chaos-in-the-cloud/</guid>
      <description>&lt;p&gt;&lt;em&gt;This is the first in a series of articles looking at chaos engineering in general, and in particular how we&#xA;can use Amazon&amp;rsquo;s &lt;a href=&#34;https://aws.amazon.com/fis&#34;&gt;Fault Injection Service&lt;/a&gt; to test the resilience of our AWS systems.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;When I first started developing, we wrote huge, monolithic applications either running&#xA;locally on our desktops, or in our datacenters. We&amp;rsquo;d write applications that had&#xA;tens or even hundreds of thousands of lines of code. However, the applications we wrote usually consisted of&#xA;a single component, maybe two if we used a database, handling all of the logic and functionality within a&#xA;single application. Whilst this meant that we usually had complex, hard to navigate, code bases, it did mean&#xA;that in terms of architecture, our applications were relatively simple.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
