October 2017: Continuous Delivery with Containers
Details
Continuous Delivery with Containers
Talk 1: Daniel Bryant - Continuous Delivery with Containers: The Good, the Bad, and the Ugly
Implementing a continuous delivery (CD) pipeline is not trivial, and the introduction of container technology to the development stack can introduce additional challenges and requirements. In this talk you will look at the high-level steps that are essential for creating an effective pipeline for creating and deploying containerized applications.
Topic covered include (time permitted!):
• The impact of containers on CD
• Adding metadata to container images
• Validating NFR changes imposed by executing Java applications within a container
• Lessons learned the hard way (in production)
A supporting O'Reilly report "Containerizing Continuous Delivery in Java" will also be available, and this contains instructions and code for how to create a Jenkins-based continuous delivery pipeline that takes a series of Java applications and containerizes them, ready for functional and nonfunctional testing, and ultimately, deployment.
Daniel Bryant works as an Independent Technical Consultant, and is the CTO at SpectoLabs. He currently specialises in enabling continuous delivery within organisations through the identification of value streams, creation of build pipelines, and implementation of effective testing strategies. Daniel’s technical expertise focuses on ‘DevOps’ tooling, cloud/container platforms, and microservice implementations. He also contributes to several open source projects, writes for InfoQ, O’Reilly, and Voxxed, and regularly presents at international conferences such as OSCON, QCon and JavaOne.
@danielbryantuk (https://twitter.com/danielbryantuk)
Talk 2: Marcus Robinson & Alex Carter - Containerisation of a Legacy Software Solution
This is the story of how we took a legacy solution and pushed it into containers on Windows in just three days. After one further day, it was fully working! This was also a great chance to work with Microsoft at the cutting edge of their work on containerisation, VSTS and Azure. Case study: https://microsoft.github.io/techcasestudies/devops/2017/06/16/Callcredit_DevOps.html
@techdiction (https://twitter.com/techdiction), @smileandeliver (https://twitter.com/smileandeliver)
Talk 3: Harry Winser - Consumer Driven Contract Testing with Pact and Docker
Continuous Delivery of Microservices is hard. Instead of one monolithic application, there’s now a plethora of applications all talking via defined API calls. But how does a team ensure that a change to Service A’s API won’t affect Service B’s consumption of A’s API? What about versioning APIs? What happens if service A removes a field without service B knowing about it?
Consumer Driven Contracts (CDC), popularised by Martin Fowler (article – written by Ian Robinson), is a way for a Consuming Service to define what it expects as a response from a Providing Service when calling the Providers API.One of the most prevalent implementation of CDC’s is Pact; originally created by realestate.au. Pact provides a framework and a definition of CDC’s, which has spawned numerous implementations across a multitude of languages.By adding Pacts to a delivery pipeline, a team can automate the testing between two services to ensure that they can communicate when released.
In this talk, Harry Winser will be looking at how Consumer Driven Contracts were implemented between teams that look after over 50 different Microservices. The talk will cover the concepts of CDC’s, and how they can be leveraged to achieve fully independent releases of Microservices across teams, and how to handle a Service Rollback while still serving over 47 million requests a day. It will also look at the tools that were used, such as Docker and how it enabled easier testing for Developers.
@hazz223 (https://twitter.com/hazz223)
