<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Istio on alexos.dev</title>
    <link>https://alexos.dev/tags/istio/</link>
    <description>Recent content in Istio on alexos.dev</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Thu, 23 May 2019 20:00:00 -0100</lastBuildDate>
    <atom:link href="https://alexos.dev/tags/istio/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>KubeCon - Service Meshes</title>
      <link>https://alexos.dev/2019/05/23/kubecon-service-meshes/</link>
      <pubDate>Thu, 23 May 2019 20:00:00 -0100</pubDate>
      <guid>https://alexos.dev/2019/05/23/kubecon-service-meshes/</guid>
      <description>&lt;figure&gt;&lt;img src=&#34;https://alexos.dev/images/sailboat.jpg?width=600px&amp;amp;classes=shadow&#34;&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;So, why service meshes? &lt;del&gt;Because I am architect, and architects are born to love service meshes.&lt;/del&gt; Because actually I can totally see the value of a service mesh, I just can&amp;rsquo;t quite seem to convince anyone that they&amp;rsquo;re worth biting the bullet on yet.&lt;/p&gt;&#xA;&lt;p&gt;It&amp;rsquo;s a design pattern I&amp;rsquo;m totally sold on and just need to find the killer need for so we can start reaping some of those sweet, sweet benefits. Or crying at the complexity and brittle overlay we&amp;rsquo;ve subjected ourselves too. Maybe.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
