Docker/DevOps Meetup: Metrics-Driven Continuous Performance and Scalabilty

Editor's Notes

• #2: Get Dynatrace Free Trial at http://bit.ly/dtpersonal Video Tutorials on YouTube Channel: http://bit.ly/dttutorials Online Webinars every other week: http://bit.ly/onlineperfclinic Share Your PurePath with me: http://bit.ly/sharepurepath More blogs on http://blog.dynatrace.com
• #3: If you are new to DevOps and Continuous Delivery check out these two books: Continuous Delivery from Jez Humble, David Farley and The Phoenix Project from Gene Kim, Kevin Behr, and George Spafford
• #4: Many companies that have a „DevOps Strategy“ too often just follow the Unicorns
• #5: Several companies changed their way they develop and deploy software over the years. Here are some examples (numbers from 2011 – 2014) Cars: from 2 deployments to 700 Flicks: 10+ per Day Etsy: lets every new employee on their first day of employment make a code change and push it through the pipeline in production: THAT’S the right approach towards required culture change Amazon: every 11.6s Remember: these are very small changes – which is also a key goal of continuous delivery. The smaller the change the easier it is to deploy, the less risk it has, the easier it is to test and the easier is it to take it out in case it has a problem.
• #6: If „Being DevOps“ just means you just increase the number of deployments then you are bound to fail. Here is an example of a bad web application. When deploying this more frequently you will end up in more war rooms
• #7: Another example from a SharePoint app that allows production deployments by SharePoint Admins. A simply change directly in production can have very negative impacts, e.g: deploying a new WebPart with a Data-Driven Performance Hotspot
• #8: Don‘t just copy the Unicorns – dont be just driven the number of deployments.
• #9: The problem is though – when you blindly copy what you read you may end up with a very ugly copy of a Unicorn. Its not about copying everything or thinking that you have to release as frequently as the Unicorns. It is about changing and adapting a lot of their best practices but doing it in a way that makes sense to you. For you it might be enough to release once a month or once week.
• #10: Listen to the next generation Unicorns, e.g: those talking at Velocity or other conferences: Target, CapitalOne, IG, ...
• #11: These are the highlights of these talks for me this year: http://apmblog.dynatrace.com/2015/05/27/velocity-2015-our-conference-highlights/ http://apmblog.dynatrace.com/2015/05/28/velocity-2015-highlights-from-day-2/ http://apmblog.dynatrace.com/2015/05/29/velocity-2015-highlights-from-last-day/
• #12: Despite all these stories the main Challenge remains ...
• #13: Don’t’ just try to deploy faster …
• #14: … as you may just ending up failing faster and more often!
• #15: Don’t become the next headline on the news as United in the summer of 2015
• #16: Or the Fifa World Cup App that crashed for 80% of their Android Users caused by a memory leak in an outdated UI Library one week before the WorldCup
• #18: I love metrics – and I think we should make decisions on deployments based on key metrics. But also monitor deployments in production to learn whether the deployment was really good
• #19: The BASIC Metric EVERYONE has to have: Synthetic Availability Monitoring -> Clearly something went wrong
• #20: Even if the deployment seemed good because all features work and response time is the same as before. If your resource consumption goes up like this the deployment is NOT GOOD. As you are now paying a lot of money for that extra compute power: http://apmblog.dynatrace.com/2015/06/30/fighting-technical-debt-memory-leak-detection-in-production/ http://apmblog.dynatrace.com/2014/10/28/hands-tutorial-5-steps-identify-java-net-memory-leaks/
• #21: Layer Breakdown perfectly shows which layer of your app is not scaling: http://apmblog.dynatrace.com/2015/01/22/key-performance-metrics-load-tests-beyond-response-time-part/
• #22: Got a marketing campaign? If you roll it out do it smart: Start with a small number – monitor user behavior – fix errors if there are any before rolling out the rest of the campaign: http://apmblog.dynatrace.com/2015/02/26/omni-channel-monitoring-in-real-life/
• #23: http://apmblog.dynatrace.com/2015/11/30/last-minute-rescue-for-black-friday-business/
• #24: A lot of people dont look at these metrics and just add new code on an ever growing big pile of technical debt
• #25: Based on a recent study: 80% of Dev Team overall is spent in Bugfixing instead of building new cool features $60B annual costs of bad software instead of investing it in new cool features to spearhead competition
• #26: Yes – we are focusing on quality TOO LATE
• #27: When its too late we end up here
• #28: We need to leave that status quo. And there are two numbers that tell us that it is not as hard to do as it may seem
• #29: Based on my experience 80% of the problems are only caused by 20% problem patterns. And focusing on 20% of potential problems that take away 80% of the pain is a very good starting point
• #30: Sounds super nice on paper – so – how do we get there?
• #35: This story is from Joe – a DB guy from a very large telco arguing with his developers over performance problems of an online room reservation system which has evolved from a small project implemented by an intern to an application that is now used in their entire organization
• #36: Devs buillt custom monitoring to proof their point! Contradicting what Joe‘s DB Tools had to say
• #37: Reading this Transaction Flow showed what the real problem was: Loading Too Much Data from the Database causing High Memory Usage and therefore high CPU to cleanup the garbage
• #38: Every SQL was executed on its on Connection
• #39: The intern back then implemented its own OR Mapper by loading the full database content into a HashTable using individual queries
• #44: This was a monolithic app for searching sports club websites. The executed sample search brought 33 sports club. Before this app was „migrated“ to Microservices everything was in a single monolith taking about 1s to execute. After the „migration“ to (micro)services the same call takes 26.7s including 33 calls to the new microservice and 171 roundtrips to the database
• #48: A Mobile App with a GPS Distance Calculation Problem. Couldnt be found in test – so they moved the Test to Production to find out which devices actually have the problem http://apmblog.dynatrace.com/2013/07/23/too-fast-for-the-user/
• #49: As many mobile apps – you might rely on 3rd party services for your users to login. Make sure you monitor the response time and success of these calls and how it impacts your end users
• #53: Overloaded Kia website brings it down during superbowl: http://apmblog.dynatrace.com/2014/03/05/bloated-web-pages-can-make-or-break-the-day-lessons-learned-from-super-bowl-advertisers/
• #54: GoDaddy is doing something different: they have a special „bare minimum static optimized“ website for the spike period -> thats smart: http://apmblog.dynatrace.com/2014/02/19/dns-tcp-and-size-application-performance-best-practices-of-super-bowl-advertisers/
• #57: So – we have seen a lot of metrics. The goal now is that you start with one metric. Pick a single metric and take it back to your engineering team (Dev, Test, Ops and Business). Sit down and agree on what this metric means for everyone, how to measure it and also how to report it Also remember that for most of these use cases discussed and metrics derived from it we only need a single user test. Even though we can identify performance, scalability and architectural issues – in most cases we don’t need a load test. Single user tests or unit tests are good enough
• #61: If you are already executing tests than that is great – BUT – you are only testing functionality. It is time to look „underneath“ the hood and automaitcally find all these other problems we just talked about by looking at the right metrics
• #62: Here is how we do this. In addition to looking at functional and unit test results which only tell us how functionality is we also look into these backed metrics for every test. With that we can immediately identify whether code changes result in any performance, scalability or architectural regressions. Knowing this allows us to stop that build early
• #63: This is how this can look like in a real life example. Analyzing Key Performance, Scalability and Architectural Metrics for every single test
• #64: Dynatrace can either show the data in our own dashboards or you can integrate this data through our REST APIs with your Build Server such as Jenkins, Bamboo, .... And even „BREAK THE BUILD“ if something is bad!
• #65: Make sure you do not end in Pre-Production. Once you deploy your application you also want to monitor how your application is doing in the wild. Same technical metrics are important to monitor but also correlate them with the business metrics such as Conversion Rates, Bounce Rates, Revenue, ...
• #66: Docker Fans: Make sure you monitor your Docker Enviornments to identify any bottlenecks – whether caused by Docker or by your app making inefficient use of Docker/Container resources! http://apmblog.dynatrace.com/2015/07/21/how-to-get-visibility-into-docker-clusters-running-kubernetes/
• #67: More screenshots and tips and tricks on docker/container monitoring http://apmblog.dynatrace.com/2015/07/21/how-to-get-visibility-into-docker-clusters-running-kubernetes/
• #68: A „dockerized“ app monitored with Dynatrace http://apmblog.dynatrace.com/2015/07/21/how-to-get-visibility-into-docker-clusters-running-kubernetes/
• #74: So – our goal is to deploy new features faster to get it in front of our paying end users or employees
• #75: Become the next generation Unicorn!