Tweet
Tweet

Slide 1

Slide 1 text

Continuous Delivery in the Wild

Slide 2

Slide 2 text

Dave Karow Continuous Delivery Evangelist, Split @davekarow Pete Hodgson Independent software delivery consultant @ph1

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

Financial Services Startup Founded in 2007, with around 800 engineers working on an SOA with a large number of small services. Payment Processor Founded in 2009, with around 1000 engineers and Service-Oriented Architecture (SOA) consisting of around 500 services. Continuous Delivery in the Wild Research Methodology and Participants Automotive Marketplace Has had an online presence since the mid-1990s, with around 200 engineers and an architecture that's migrating from monolithic web apps toward SOA, with currently around 300 services. Online Retailer Founded in the 1950s, with around 20 engineers working on a monolithic web application, which is just starting to move toward SOA. Food Delivery Service Founded in 2012, with around 30 engineers working on an SOA of 15 to 20 services. Healthcare Provider Founded in 2007, with around 100 engineers working on a monolithic web application. Print and Design Service Founded in 2004, with around 50 engineers who are partway through a migration from a monolithic web application to SOA, with currently around 50 services. Online Realtor Founded in 1995, with around 450 engineers working on an SOA made of up of both large monolithic systems and smaller services.

Slide 5

Slide 5 text

Path to Production Continuous Delivery in the Wild

Slide 6

Slide 6 text

Agenda - Reducing batch size - How Architecture impacts Release Management - Branch management: two modes of CD - Delivery platforms Continuous Delivery in the Wild

Slide 7

Slide 7 text

Reducing Batch Size Continuous Delivery in the Wild

Slide 8

Slide 8 text

Reducing batch size Continuous Delivery in the Wild

Slide 9

Slide 9 text

Reducing batch size Continuous Delivery in the Wild

Slide 10

Slide 10 text

Forsgren PhD, Nicole. Accelerate . IT Revolution Press

Slide 11

Slide 11 text

Reducing Batch Size Continuous Delivery in the Wild

Slide 12

Slide 12 text

Architecture and Release Management Continuous Delivery in the Wild

Slide 13

Slide 13 text

SOA vs Monoliths Continuous Delivery in the Wild

Slide 14

Slide 14 text

Architecture and Release Management Continuous Delivery in the Wild

Slide 15

Slide 15 text

Continuous Delivery in the Wild Branch Management

Slide 16

Slide 16 text

Github Flow Continuous Delivery in the Wild

Slide 17

Slide 17 text

Trunk-based Development Continuous Delivery in the Wild

Slide 18

Slide 18 text

Continuous Delivery in the Wild

Slide 19

Slide 19 text

Branch Management Continuous Delivery in the Wild

Slide 20

Slide 20 text

Custom Delivery Platforms Continuous Delivery in the Wild

Slide 21

Slide 21 text

Capabilities of a Delivery Platform Continuous Delivery in the Wild ● Deploying a specific version of a service into an environment ● Requesting a hold on production deployments ● Signing off on a version as being ready for production ● Tracking which version of each service is deployed into an environment ● Showing a history of previous deployments ● Reporting which new versions of a service are available for deployment ● Performing data management tasks in an environment (such as reseeding test data or importing scrubbed production data) ● Reporting overall service health in an environment ● Providing a Service Registry—a way to view metadata about the service in an environment, such as team ownership, service dependencies, and quick links to production dashboards

Slide 22

Slide 22 text

Custom Delivery Platforms Continuous Delivery in the Wild

Slide 23

Slide 23 text

Q & A