The Pillars of Continuous Delivery

Copyright © 2019,eProseed and/or its affiliates. All rights reserved. | Confidential
THE PILLARS OF
CONTINUOUS DELIVERY
DOAG 2019
Lykle Thijssen, November 19, 2019

ABOUT ME
Principal Architect at eProseed
Scrum Master
Oracle ACE Associate
SOA/BPM
Microservices
2

THE PILLARS OF CONTINUOUS DELIVERY
Continuous Delivery
Agile
Microservices
Automation
Cloud
1
2
3
4
5
3

CONTINUOUS DELIVERY – DEFINITION
What is Continuous Delivery?
“Continuous delivery is a software engineering approach in which teams produce
software in short cycles, ensuring that the software can be reliably released at any time”
4

CONTINUOUS DELIVERY – PURPOSE
What is the purpose of Continuous Delivery?
“It aims at building, testing, and releasing software with greater speed and frequency.”
5

CONTINUOUS DELIVERY – WHY
Why would you want Continuous Delivery?
“The approach helps reduce the cost, time, and risk of delivering changes by allowing for
more incremental updates to applications in production.”
6

CONTINUOUS DELIVERY – CONDITION
What do you need for Continuous Delivery?
“A straightforward and repeatable deployment process is important for continuous
delivery.”
7

AGILE
Why is an Agile development process important for Continuous Delivery?
– Shorter release cycles
– Early feedback
– Fail fast, learn quickly
– Flexible to change
– Dev and Test working in parallel
– Shippable product after every sprint
– Fun!
8

MICROSERVICES
Why is a Microservices architecture important for Continuous Delivery?
– Design time dependencies
– Runtime dependencies
– Products, not projects
– Cross-functional teams
9

DEVOPS
What about DevOps?
– Dev and Ops working together
– Perfect fit for Agile and Microservices
– “You Build It, You Run It”
– Responsible for full lifecycle of the product
– DevOps is a culture, not a team!
10

AUTOMATION
What is Automation?
“Automation is the technology by which a process or procedure is
performed with minimal human assistance”
11

TEST AUTOMATION
Why is Test Automation important for Continuous Delivery?
– Quality control
– Automate repeatable steps
– Test upon every deployment
– Test every day/night
– Broader test coverage
12

TEST AUTOMATION
Why do we still need manual testing?
– User acceptance
– Initial test before automation
– Confidence
– Not everything is suitable for automation
13

DEPLOYMENT AUTOMATION (CONTINUOUS INTEGRATION)
Why is deployment automation important for Continuous Delivery?
– Repeatable steps
– Controlled flow
– Less prone to errors
– Helps Test Automation
– Nightly builds & deploys
– Significantly faster
– No need for extensive handovers
14

CLOUD
Why is cloud important for Continuous Delivery?
– Easier to setup
– Easier to scale
– Less waiting time
– Security & configuration
– Unlimited space
Keep the budget in mind!
15

CONCLUSION
Continuous Delivery requires changes that are:
– Organizational
– Technical
– Architectural
Take one of these pillars out and ...
16

Mobile Process /
Integration
Analytics /
Big Data
Database /
Data
Management
Identity &
Access
Management
Oracle Cloud
eProseed Confidential17

The Pillars of Continuous Delivery

More Related Content

What's hot (18)

Similar to The Pillars of Continuous Delivery (20)

Recently uploaded (20)

The Pillars of Continuous Delivery