Blue-green deploymentIn practice

devops Journey@LATAM

Agenda

❏¿Que es Blue-green deployment?

❏¿Cual son su beneficios y custos?

❏¿Qué cuidados tenemos que tomar?

❏Blue-green en practica

Cómo podremos poner software en producción y minimizar el downtime?

Cómo podremos hacer rollback rapidamente?

ver 1.0

ver 0.9

ver 1.0

ver 1.1

ver 1.0

ver 1.1

Sounds good!But is there something we might need to watch out?

Things to watch out

❏Infrastructure

❏Shared underlying infrastructures (VMs, Docker)

❏Long running transactions on current environment

❏Backward incompatible changes

❏Database migrations

❏ Changes on APIs response

Dealing with backward incompatibility

❏Expand and contract strategy

❏Works for changes on:

❏ API contracts breaks

❏ DB Changes

❏ Dependent systems (Sabre, coordinated microservices changes)

Changing DB schema

❏Separate deploy:

❏ Schema changes

❏ Application upgrades

❏DB refactoring + current application version = rollback point

Expand and contract applied on DB changes

❏Apply a database refactoring

❏ expand DB

❏Deploy the database refactoring

❏ expand app

❏Remove the support to older schema

❏ contract db and app

Live demoWhen the things usually don't work as expected...

Muchas gracias!lbeier@thoughtworks.com

github.com/tutabeier#deliverysquad#deliverytribe