<img height="1" width="1" src="https://www.facebook.com/tr?id=&amp;ev=PageView &amp;noscript=1">

Tom Stockton

Find me on:

Recent Posts

Posted by Tom Stockton
Wed, Mar 11, 2015

Update - 12/3/15

Since publishing this blog a couple of days ago we have been fairly overwhelmed by the interest in it.  I had some feedback from the man behind ConductR (Christopher Hunt from Typesafe) who put me straight on my comparison with Mesos and Marathon.  It turns out that ConductR is not designed to replace Mesos, but rather to work with it as a highly available scheduler in the same way that Marathon does.  The main differentiator for ConductR is that is aimed specifically at deploying and managing Typesafe Reactive Platform based apps and services.

In its current implementation, ConductR does not integrate with Mesos, instead it provisions its own basic resource provider on which to deploy applications.  Christopher tells me that Mesos integration will be worked on during the second quarter of this year .... watch this space!


Having recently used to deploy a infrastructure as well as the via containers, I was very interested to see how have interpereted this potentially game changing way of deploying applications.

Posted by Tom Stockton
Fri, Jan 9, 2015

Posted by Tom Stockton
Thu, Dec 11, 2014

Posted by Tom Stockton
Tue, May 27, 2014

What is this?

Martin Fowler provides a fairly definitive explanation of this () so I’ll try not to regurgitate what he’s written too much! However, in my mind (and in my own words) I’d say that blue green is about 'getting the latest version of your software into production as quickly and efficiently as possible'. Essentially it involves creating a (green) version of your existing (blue) system with your latest code deployment, then (after confirming it works) switching end user requests to use the green version.  If there are any issues then you can easily roll back to blue and forget green ever happened.

Recent Posts

Posts by Topic

see all

Subscribe to Email Updates