Continuous Delivery – Quantity vs. Quality Karsten Flott

Continuous Delivery – Quantity vs. Quality
Karsten Flott
BANK
Today
Yesterday
Business Defined Software – requires Continuous Delivery
Copyright © 2014 AppDynamics. All rights reserved.
2
Enterprises strived for the ‘single pane of glass’
Copyright © 2015 AppDynamics. All rights reserved.
3
But ended up with a ‘single glass of pain’
Copyright © 2015 AppDynamics. All rights reserved.
4
Challenge 1: New Ideas = increase
complexity
Copyright © 2014 AppDynamics. All rights reserved.
5
Continuous Delivery – Starting here
Login
Flugstatus
Flugsuche
Bezahlen
Copyright © 2014 AppDynamics. All rights reserved.
6
Continuous Delivery – Ending here
Agile
SOA
Login
Flugstatus
Cloud
Mobile
Flugsuche
Bezahlen
Web
NOSQL
Big data
Copyright © 2014 AppDynamics. All rights reserved.
7
Continuous Delivery – Ending here
Copyright © 2014 AppDynamics. All rights reserved.
8
Challenges
•  Direct relation of components require testing the
behavior of whole application instead of single functions
•  Tests are more complex and time intensive
•  Becoming more and more less flexible
Copyright © 2015 AppDynamics. All rights reserved.
9
Challenge 2: Reduce cost = Near-/OffShoring
Copyright © 2014 AppDynamics. All rights reserved.
10
Delivery of functions – no performance context
Transaction: ViewListOfTopSellers
Copyright © 2014 AppDynamics. All rights reserved.
11
Challenges
•  Performance is not part of their task (contractual) – just
function driven
•  Risk of less skilled people building solution which has to
run in enterprise environments
•  In my environment is it fast … must be you
–  Mean Time to Innocence – increase delay for go live
Copyright © 2015 AppDynamics. All rights reserved.
12
Challenge 3: Adapting Processes
Copyright © 2014 AppDynamics. All rights reserved.
13
Deploy of new features … anytime?
Copyright © 2014 AppDynamics. All rights reserved.
14
Challenges
•  Deployments need to be well planned
•  Cannot test any situation
Copyright © 2015 AppDynamics. All rights reserved.
15
Requirements on Performance Monitoring
in a Continuous Delivery Environment
Copyright © 2014 AppDynamics. All rights reserved.
16
Continuous Delivery Aims – Fast & successful Deploys
•  Fasten release cycles through automated build-pipelines
–  Require succeeded tests
•  Any build which reaches the end stage can be put in
production automatically or by pressing a button
•  Requirements:
–  Automated as much as possible
–  Fully reproducible
–  Fast feedback required
à Fast and stable build pipeline and software of high quality
Copyright © 2015 AppDynamics. All rights reserved.
17
Continuous Delivery Aims
Copyright © 2015 AppDynamics. All rights reserved.
18
Continuous Delivery Aims
Copyright © 2015 AppDynamics. All rights reserved.
19
… the biggest problem; TESTING
•  New features come fast and in small increments
à Performance impact small and hard to measure
•  Tools like Jmeter, LoadRunner, Grinder etc. are great in generating load
and measuring Performance outside the App as black box
à But it is insufficient to measure small fluctuations impacted from new
features
•  Application Performance Management Solutions need to be in place in
the whole Application Lifecycle
à 
à 
à 
à 
In prod = reduce mean time to innocence
In test and dev = find the small increase in method execution - Baseline
Transparency in dependencies through changes
Getting fast feedback through tests
Copyright © 2015 AppDynamics. All rights reserved.
20
Application Performance Management in
Production and Test gives you the ….
Copyright © 2015 AppDynamics. All rights reserved.
21
appdynamics.com/demo
appdynamics.com/freetrial
karsten.flott@appdynamics.com
THANK YOU