docker and continuous delivery - amsterdam 26-11-2015 - docker randstad meetup

Docker and Continuous Delivery

How containers make achieving Continuous Delivery easier and why they are not enough to create a successful Continuous Delivery process 

Docker Randstad meetup, 26-11-2015Amsterdam, KPNPavel Chunyayev

@PavelChunyayev

Amsterdam

Levi9 HQAmsterdam – 2005

25 people

Novi Sad

SerbiaNovi Sad – 2005

320+ people

Zrenjanin

SerbiaZrenjanin– 2014

30+ people

Iasi

RomaniaIasi – 200780+ people

Kiev

UkraineKiev – 2008130+ people

@PavelChunyayev

Electronic Retail

DigitalMarketing

Traffic and Transport

Software Services

@PavelChunyayev

Customer satisfaction 2015

• 4th year great results in Outsourcing Performance study

• 2015: 100% customer recommendation scoreExcellent trust score

@PavelChunyayev

About me• 11 years of IT experience• Lived and worked in Ukraine and Estonia • Moved a year ago to the Netherlands

• Learning Dutch• Love cycling

• Support me with Holandse 100

Continuous Delivery

Safely, rapidly and predictably deliver new features to production

@PavelChunyayev

Continuous Delivery

• Faster time to market

• How many deployments a day?

• Time between committing line of code and running in 

production

It’s not only about speed

@PavelChunyayev

It’s not only about speed• Some companies have different agenda• Some need pure speed and time to market• Some want controlled and predictable process• Some want to ensure that quality of their applications is of a certain level and complies with requirements

@PavelChunyayev

It’s not only about speed• It's not just about automating deployments.• It’s not about executing pipeline over and over again

But:• Organization of the right process to support continuous feature delivery, improvements and learning.• Organization proper testing to be able to deliver at high speed.

Quality > Speed

Docker

Docker doesn’t solve a lot of issues

Docker solves exactly one and brilliantly

Infrastructure

New way to manage Infrastructure

CDBuild • Test • Deploy

DockerBuild • Ship • Run

@PavelChunyayev

Continuous Delivery pipeline

Inception Plan Develop Integrate Test Release Operate

Integrate Deploy to test Test Deploy to 

staging Test Release

@PavelChunyayev

• Business ideas are generated• Responsibility of product management / program management• Ideas need validation • Flow time is very important

• Docker has nothing to do with it

Inception Plan Develop Integrate Test Release Operate

@PavelChunyayev

• Ideas are refined into epics and stories.• Requirements, test and acceptance criteria are created

Given that feature is available on the websiteWhen I open the website Then I’m immediately impressedAnd I’d like to spend all my money

• Docker has nothing to do with it

Inception Plan Develop Integrate Test Release Operate

@PavelChunyayev

• Code is created along with tests and anything else that is required to deliver the feature to production.

• Developers need:• Production-like local environment• Quick to start• Repeatable and reproducible• Fast feedback

Inception Plan Develop Integrate Test Release Operate

@PavelChunyayev

• First CD stage with Docker• Running local environments has never been easy• Most of the popularity of Docker is thanks to developers• Most companies have started evaluating Docker here (some are even late for Vagrant)

• No mocking!

Inception Plan Develop Integrate Test Release Operate

@PavelChunyayev

• Most people experience CD starting from Build/Integration stage• Continuous Integration is a fundamental practice• It’s common to advise against feature branches and commit directly to master• Still you can make feature branches work• Short lived• Constantly updated against master

Inception Plan Develop Integrate Test Release Operate

@PavelChunyayev

• Docker is very helpful:• Build containers• Run CI in containers • Create self-build containers

• Some people go as far as completely get rid of CI:• Build and integrate containers• Scheduled as hooks automatically • Still not most companies want 

• Microservices are a lot easier with containers

Inception Plan Develop Integrate Test Release Operate

@PavelChunyayev

• You need to invest heavily in automated testing• Bear testing pyramid in mind

• Move tests to the left• Run all the tests all the time• Over and over again

• If you can’t do it, you have wrong tests!

Inception Plan Develop Integrate Test Release Operate

ME2E

ContractComponentIntegration

Unit

@PavelChunyayev

• Docker environments for each kind of tests • Always fresh• Quick• Up-to-date• Immutable infrastructure!

• Docker can also help with testing infrastructure as well

Inception Plan Develop Integrate Test Release Operate

@PavelChunyayev

Inception Plan Develop Integrate Test Release Operate

Testing in production

@PavelChunyayev

• Release != deployment

• Independently releasable microservices

• Blue-green, canary, rolling deployments

Inception Plan Develop Integrate Test Release Operate

@PavelChunyayev

• Docker shines here• Easy and uniform deployment• Complex environments - better with additional tools

Inception Plan Develop Integrate Test Release Operate

@PavelChunyayev

• This is where money is generated• This is where ideas are validated

• Monitor business metrics• Focus on MTTD and MTTR

• Distributed systems are hard to operate

Inception Plan Develop Integrate Test Release Operate

@PavelChunyayev

• Scaling is easy• Phoenix servers

• Monitoring of containers can be hell – new products are emerging

• Running distributed systems is hard, containers make it a bit easier. 

Inception Plan Develop Integrate Test Release Operate

CDBuild • Test • Deploy

DockerBuild • Ship • Run

@PavelChunyayev

Takeaways• Docker doesn’t:• Solve quality for you• Create good product ideas• Improve your software development process

• Docker creates:• New ways to manage infrastructure• New ways to run applications in production

pavel@levi9.com

Any questions?