Embed Size (px)
Citation preview
Continuous Delivery – Quantity vs. Quality
Karsten Flott
2
Yest
erda
y To
day
Copyright © 2014 AppDynamics. All rights reserved.
Business Defined Software – requires Continuous Delivery
BANK
3
Enterprises strived for the ‘single pane of glass’
Copyright © 2015 AppDynamics. All rights reserved.
4
But ended up with a ‘single glass of pain’
Copyright © 2015 AppDynamics. All rights reserved.
Challenge 1: New Ideas = increase complexity
Copyright © 2014 AppDynamics. All rights reserved. 5
Login
Flugstatus
Flugsuche
Bezahlen
Copyright © 2014 AppDynamics. All rights reserved. 6
Continuous Delivery – Starting here
Login
Flugstatus
Flugsuche
Bezahlen
Copyright © 2014 AppDynamics. All rights reserved. 7
Mobile
Big data
SOA
NOSQL
Cloud
Agile
Web
Continuous Delivery – Ending here
Copyright © 2014 AppDynamics. All rights reserved. 8
Continuous Delivery – Ending here
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-/Off- Shoring
Copyright © 2014 AppDynamics. All rights reserved. 10
Copyright © 2014 AppDynamics. All rights reserved. 11
Delivery of functions – no performance context
Transaction: ViewListOfTopSellers
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
Copyright © 2014 AppDynamics. All rights reserved. 14
Deploy of new features … anytime?
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
THANK YOU
