<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Microservices on Benny Simmonds</title>
    <link>https://www.bencode.io/tags/microservices/</link>
    <description>Recent content in Microservices on Benny Simmonds</description>
    <generator>Hugo -- 0.149.1</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 26 Apr 2015 22:09:01 +0000</lastBuildDate>
    <atom:link href="https://www.bencode.io/tags/microservices/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Microservices</title>
      <link>https://www.bencode.io/posts/2015-04-26-microservices/</link>
      <pubDate>Sun, 26 Apr 2015 22:09:01 +0000</pubDate>
      <guid>https://www.bencode.io/posts/2015-04-26-microservices/</guid>
      <description>&lt;p&gt;Amped by &lt;a href=&#34;https://twitter.com/yaamehn&#34;&gt;@yaamehn&lt;/a&gt;&amp;rsquo;s opinionated &lt;a href=&#34;https://www.youtube.com/watch?v=KHqMPRA6jVI&amp;amp;list=LL5wCy3trg9aNEBcarsIWUEg&amp;amp;index=1&#34;&gt;Microservices A Reference Architecture&lt;/a&gt; recent talk at the Microservices Australia Meetup, has got me thinking about the many interesting possibilities Microservices stirs up. Many useful techniques are touched on, regardless of whether actually adopting Microservices.&lt;/p&gt;
&lt;p&gt;On the surface Microservices doesn&amp;rsquo;t appear to be anything groundbreakingly new. It does however push tried-and-trued concepts (e.g. abstraction, decoupling, modularisation, continuous delivery) to extreme levels. Fused with innovations in the operations space such as containerising like &lt;a href=&#34;https://www.docker.com/&#34;&gt;Docker&lt;/a&gt;, can lead to some very powerful outcomes; such efficient continuous delivery (on a micro scale), decoupling of domains allowing for a best of bread technlogies, and so on.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
