<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>aws chaos cloud chaos-engineering on Software Craftsman, Young Curmudgeon</title>
    <link>https://jgemedina.github.io/tags/aws-chaos-cloud-chaos-engineering/</link>
    <description>Recent content in aws chaos cloud chaos-engineering on Software Craftsman, Young Curmudgeon</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 Feb 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://jgemedina.github.io/tags/aws-chaos-cloud-chaos-engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Chaos Engineering</title>
      <link>https://jgemedina.github.io/post/2019-02-02-chaos-engineering/</link>
      <pubDate>Sat, 02 Feb 2019 00:00:00 +0000</pubDate>
      
      <guid>https://jgemedina.github.io/post/2019-02-02-chaos-engineering/</guid>
      <description>&lt;p&gt;This is a small extract from a previous post regarding &lt;a href=&#34;https://log.jorgemedina.se/tech%20cloud/2019/01/26/awsloft-resiliency-patterns.html&#34; title=&#34;Patterns for a Resilient Architecture&#34;&gt;Patterns for a Resilient Architecture&lt;/a&gt; in which we reviewed good practices and design to ensure a high degree of resliency in our systems; this was too part of a session during the past &lt;a href=&#34;https://awsloft-stockholm.com/&#34; title=&#34;AWS Loft&#34;&gt;AWS Loft&lt;/a&gt; in Stockholm on 2018.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
