http://www.dtsato.com/blog/2014/05/06/implementing-blue-green-deployments-with-aws/ We can change! Wed, 07 May 2014 20:15:42 +0000 hourly 1 https://wordpress.org/?v=4.2.20 http://www.dtsato.com/blog/2014/05/06/implementing-blue-green-deployments-with-aws/comment-page-1/#comment-665654 Wed, 07 May 2014 20:15:42 +0000 http://www.dtsato.com/blog/?p=437#comment-665654 Nice writeup – but there is one point which I think is also worth mentioning:
When using this style of deployments, and as most apps deal with a single DB across any number of clustered app server instances, the db will then be on v2 – and thus be used by both versions while both blue AND green are active (ie during the sanity checking duration of when green is still internal). This “backwards compatibility” of the db or non-breaking forward changes (whichever way you look at it) boils down to the team’s discipline in keeping this deployment style alive. I have used BG deployments before, and this particular point has to be actively/explicitly safe-guarded by the team.

]]>