<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Devops on John Hamelink</title>
    <link>https://johnhame.link/tags/devops/</link>
    <description>Recent content in Devops on John Hamelink</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>John hamelink</copyright>
    <lastBuildDate>Thu, 03 Mar 2016 02:22:00 +0000</lastBuildDate>
    <atom:link href="https://johnhame.link/tags/devops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Elixir/Erlang and autoscaled EC2 servers - how to make them best buddies</title>
      <link>https://johnhame.link/posts/elixir-and-ec2/</link>
      <pubDate>Thu, 03 Mar 2016 02:22:00 +0000</pubDate>
      <guid>https://johnhame.link/posts/elixir-and-ec2/</guid>
      <description>&lt;p&gt;At &lt;a href=&#34;https://findaplayer.com&#34;&gt;Find a Player&lt;/a&gt;, we&amp;rsquo;ve been trying to figure out how we want to cluster our&#xA;Elixir servers - so that they can share state between each other - recently.&#xA;Because we come from ruby (ie, not a high-availability background), when we want&#xA;to discover other machines in a network we&amp;rsquo;d traditionally use something like&#xA;&lt;a href=&#34;https://consul.io&#34;&gt;Consul&lt;/a&gt; - of which I wrote a ruby library called &lt;a href=&#34;https://github.com/WeAreFarmGeek/diplomat/&#34;&gt;Diplomat&lt;/a&gt; (which admittedly needs&#xA;some love).&lt;/p&gt;&#xA;&lt;p&gt;However, after chatting with &lt;a href=&#34;https://twitter.com/gordonguthrie&#34;&gt;Gordon Guthrie&lt;/a&gt; - a guy who&amp;rsquo;s been working with&#xA;Erlang for over 13 years - over twitter, he told us to checkout&#xA;&lt;code&gt;:net_adm.world/0&lt;/code&gt;. Which does pretty much exactly what we want, straight out of&#xA;the box.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Distributed Web Systems with Consul, Diplomat, Envoy and HAProxy</title>
      <link>https://johnhame.link/posts/distributed-systems-with-consul-diplomat-envoy-and-haproxy/</link>
      <pubDate>Thu, 24 Jul 2014 01:30:00 +0100</pubDate>
      <guid>https://johnhame.link/posts/distributed-systems-with-consul-diplomat-envoy-and-haproxy/</guid>
      <description>&lt;p&gt;As part as my never-ending quest to improve how I build cool things, I&amp;rsquo;ve been&#xA;working for some time on building out infrastructure to help automate and&#xA;monitor how my apps and servers are doing. &lt;a href=&#34;http://www.postdesk.com/scaling-horizontally-better-web-development&#34;&gt;I&amp;rsquo;ve written about horizontal scaling&#xA;before&lt;/a&gt;, but today I&amp;rsquo;d like to get into one specific facet of its implementation:&#xA;automated network discovery, and how we use it at &lt;a href=&#34;http://farmer.io&#34;&gt;FarmGeek&lt;/a&gt; to build reliable&#xA;applications.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-problem&#34;&gt;The Problem&lt;/h2&gt;&#xA;&lt;p&gt;So lets say you have a few servers - a node balancer, two application servers&#xA;and a database server, for example. Everything&amp;rsquo;s working fine until &lt;strong&gt;BAM&lt;/strong&gt;, one&#xA;of your application servers crashes. To make things worse, in this scenario for&#xA;an unexplained reason nobody finds out about this. However your HAProxy checks&#xA;work and so the node leaves the connection pool as expected.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
