Download to read offline
Uploaded byLee Atchison
FutureStack'19 Closing Keynote
The document discusses how modern applications require modern monitoring and processes to stay performing. It notes that modern applications operate on dynamic cloud infrastructures with constant changes, requiring monitoring of business success, application performance, and customer experience. It emphasizes the importance of managing risk through understanding and mitigating risks rather than removing risks. It also discusses how DevOps is a cultural change involving team-level responsibility and ownership. The presentation aims to explain how instrumentation, infrastructure management, risk management, and DevOps culture can help keep modern applications running effectively.
More Related Content
Similar to FutureStack'19 Closing Keynote
![Lew Cirne, FS16 Keynote [FutureStack16]](https://cdn.slidesharecdn.com/ss_thumbnails/fs16sfkeynotelewshare1-161206235025-thumbnail.jpg?width=640&height=640&fit=bounds)
![The Full Story: Managing Change at 100MPH [FutureStack16]](https://cdn.slidesharecdn.com/ss_thumbnails/879shipirodigitaldilemma111516b-161201215752-thumbnail.jpg?width=640&height=640&fit=bounds)
FutureStack'19 Closing Keynote
- 1. ©2008–19 New Relic,Inc. All rights reserved
- 2. ©2008–19 New Relic,Inc. All rights reserved Lee Atchison Senior Director Strategic Architecture at New Relic Inc. @leeatchison leeatchison KEEPING MODERN APPLICATIONS PERFORMING DRIVING INSIGHTS TO ACTION WITHIN THE ENTERPRISE
- 3. ©2008–18 New Relic,Inc. All rights reserved 3 This presentation and the information herein (including any information that may be incorporated by reference) is provided for informational purposes only and should not be construed as an offer, commitment, promise or obligation on behalf of New Relic, Inc. (“New Relic”) to sell securities or deliver any product, material, code, functionality, or other feature. Any information provided hereby is proprietary to New Relic and may not be replicated or disclosed without New Relic’s express written permission. Such information may contain forward-looking statements within the meaning of federal securities laws. Any statement that is not a historical fact or refers to expectations, projections, future plans, objectives, estimates, goals, or other characterizations of future events is a forward-looking statement. These forward-looking statements can often be identified as such because the context of the statement will include words such as “believes,” “anticipates,” “expects” or words of similar import. Actual results may differ materially from those expressed in these forward-looking statements, which speak only as of the date hereof, and are subject to change at any time without notice. Existing and prospective investors, customers and other third parties transacting business with New Relic are cautioned not to place undue reliance on this forward-looking information. The achievement or success of the matters covered by such forward-looking statements are based on New Relic’s current assumptions, expectations, and beliefs and are subject to substantial risks, uncertainties, assumptions, and changes in circumstances that may cause the actual results, performance, or achievements to differ materially from those expressed or implied in any forward-looking statement. Further information on factors that could affect such forward-looking statements is included in the filings New Relic makes with the SEC from time to time. Copies of these documents may be obtained by visiting New Relic’s Investor Relations website at ir.newrelic.com or the SEC’s website at www.sec.gov. New Relic assumes no obligation and does not intend to update these forward-looking statements, except as required by law. New Relic makes no warranties, expressed or implied, in this presentation or otherwise, with respect to the information provided.
- 5. ©2008–19 New Relic,Inc. All rights reserved IT’S YOUR BIG DAY 5 Busiest Day of the Year Black Friday Product Launch Election Day The day of the year when your company either… … makes it or breaks it
- 6. ©2008–19 New Relic,Inc. All rights reserved 6
- 7. ©2008–19 New Relic,Inc. All rights reserved 7 Your customers assume your application will work…
- 8. ©2008–18 New Relic,Inc. All rights reserved
- 9. ©2008–18 New Relic,Inc. All rights reserved
- 10. ©2008–18 New Relic,Inc. All rights reserved
- 11. ©2008–18 New Relic,Inc. All rights reserved Hours of Operation: Mon-Fri 9am-5pm ? ? ??
- 12. ©2008–19 New Relic,Inc. All rights reserved Modern Applications
- 13. ©2008–19 New Relic,Inc. All rights reserved CustomerCare AppOwners Executives Customer Care Operations Developers App Owners Marketing Picture Your Apps Here Behind every modern app are modern teams
- 14. ©2008–19 New Relic,Inc. All rights reserved 14 How is my business doing? Business Success Am I open for business? Application Performance How are customers engaging? Customer Experience Asking Important Questions
- 15. ©2008–19 New Relic,Inc. All rights reserved 15 First Deploy in AWS India AZ Java Security Vulnerability? Traffic Spike from Celebrity Tweet! New Mobile App! Flaky Ad Network? New Location Feature Experiment! Cloud Reboot! Devs Deploy Docker Acquire New Team! (They use Node.js) Apple Changes Terms of Service Key Engineer on Open Source Tool Leaves 6 million new sensors now lve! Bug Fix! DNS Outage? Try New CDN in Europe Asking Important Questions… … About Constant Change How is my business doing? Business Success Am I open for business? Application Performance How are customers engaging? Customer Experience New Aviation Service
- 16. ©2008–19 New Relic,Inc. All rights reserved KEEPING YOUR MODERN APPLICATION RUNNING 16 and…well…modern Dynamic Infrastructure Managing Risk Instrument All the Things DevOps Culture
- 17. ©2008–19 New Relic,Inc. All rights reserved KEEPING YOUR MODERN APPLICATION RUNNING 17 Dynamic Infrastructure Managing Risk Instrument All the Things DevOps Culture
- 18. ©2008–19 New Relic,Inc. All rights reserved IT’S NOT JUST STATIC 18 Ops Static Data Centers
- 19. ©2008–19 New Relic,Inc. All rights reserved IT’S NOT JUST STATIC 19 Ops Static Data Centers
- 20. ©2008–19 New Relic,Inc. All rights reserved IT’S NOT JUST STATIC 20 Dev Dynamic Cloud World Ops Static Data Centers Ops
- 21. ©2008–19 New Relic,Inc. All rights reserved DYNAMIC CLOUD INFRASTRUCTURES Dynamic Cloud Easier Scaling Faster Change Faster Response Higher Availability and Greater Application Value The way you’ve done things in the past won’t work in the future.
- 22. ©2008–19 New Relic,Inc. All rights reserved KEEPING YOUR MODERN APPLICATION RUNNING 22 Dynamic Infrastructure Managing Risk Instrument All the Things DevOps Culture
- 23. ©2008–18 New Relic,Inc. All rights reserved Real life availability story… …overheard OPs conversation... ©2008–18 New Relic, Inc. All rights reserved
- 24. ©2008–18 New Relic,Inc. All rights reserved The Conversation… “We were wondering how changing a setting on our MySQL database might impact our performance… ©2008–18 New Relic, Inc. All rights reserved
- 25. ©2008–18 New Relic,Inc. All rights reserved The Conversation… “We were wondering how changing a setting on our MySQL database might impact our performance… … but we were worried that the change may cause our production database to fail…” ©2008–18 New Relic, Inc. All rights reserved
- 26. ©2008–18 New Relic,Inc. All rights reserved The “Scary” Overheard Conversation… “… Since we didn’t want to bring down production, we decided to make the change to our backup (replica) database instead… Under Construction … but we were worried that the change may cause our production database to fail…” ©2008–18 New Relic, Inc. All rights reserved
- 27. ©2008–18 New Relic,Inc. All rights reserved The “Scary” Overheard Conversation… … After all, it wasn’t being used for anything at the moment.” Under Construction ©2008–18 New Relic, Inc. All rights reserved “… Since we didn’t want to bring down production, we decided to make the change to our backup (replica) database instead…
- 28. ©2008–18 New Relic,Inc. All rights reserved The “Scary” Overheard Conversation… Under Construction X ©2008–18 New Relic, Inc. All rights reserved Until, of course, the backup was needed…
- 29. ©2008–18 New Relic,Inc. All rights reserved The “Scary” Overheard Conversation… This was a true story Under Construction !!! ! X X ©2008–18 New Relic, Inc. All rights reserved Until, of course, the backup was needed…
- 30. ©2008–19 New Relic,Inc. All rights reserved ALL SYSTEMS HAVE RISK IN THEM Risk is a measure of the likelihood of an undesirable event occurring Server will crash Database will get corrupted Returned answer will be incorrect Network connection will fail Newly deployed piece of software will fail There is risk that a …
- 31. ©2008–18 New Relic,Inc. All rights reserved Risk On the surface… Keeping an application running requires removing risk… But the reality is… More and more complicated systems… …makes this less and less possible. Removing surprises… Removing risk is not a viable option.
- 32. ©2008–18 New Relic,Inc. All rights reserved Living with Risk Knowing what your risk is Knowing how much risk is acceptable Knowing what you can do to mitigate the risk Risk Management is at the heart of building highly available systems Risk Management is not about Removing Risk it’s about Understanding & Mitigating Risk
- 33. ©2008–18 New Relic,Inc. All rights reserved Keeping Your Modern Application Running 33 Dynamic Infrastructure Managing Risk Instrument All the Things DevOps Culture
- 34. ©2008–19 New Relic,Inc. All rights reserved DEVOPS 34 Is Not… A Migration Is Not… A Product Change Is Not Entirely… A Process Change
- 35. ©2008–19 New Relic,Inc. All rights reserved 35 DevOps Is… A Cultural Change DEVOPS
- 36. ©2008–19 New Relic,Inc. All rights reserved DEVOPS 36 Your teams will change… Key to DevOps: Team level ownership Deploy Applications Respond to Problems Develop Applications Monitor Applications
- 37. ©2008–19 New Relic,Inc. All rights reserved DEVOPS & CLOUD 37 DevOps Adoption requires Cloud Adoption Cloud Adoption requires DevOps Adoption They are both important… for either to succeed
- 38. ©2008–19 New Relic,Inc. All rights reserved KEEPING YOUR MODERN APPLICATION RUNNING 38 Dynamic Infrastructure Managing Risk Instrument All the Things DevOps Culture
- 39. ©2008–19 New Relic,Inc. All rights reserved 39 Anticipate and Predict (analyze trends) Notice and Acknowledge (alert on problems) Diagnose and Resolve (determine what’s wrong) Continuous Monitoring Enables You to… MTTD Mean Time To Detection MTTR Mean Time To Recovery PROBLEMS CAN COME FROM ANYWHERE
- 40. ©2008–19 New Relic,Inc. All rights reserved WHY MONITORING MATTERS
- 41. ©2008–19 New Relic,Inc. All rights reserved SUCCESS IN SOFTWARE ANALYTICS Application Performance Customer Experience Business Outcome 41
- 42. ©2008–19 New Relic,Inc. All rights reserved 42 SOFTWARE MEASUREMENT FRAMEWORK Software Business • Daily Revenue • Cart Value / Volume • What do you sell? Customer Experience • Conversion Rates • Engagement / Interactions • End-User Performance Application Performance & Infrastructure • App performance • Slow Queries • Burst & Scale Engineering Velocity • Lead Time • Deploys • MTTR Service Quality • Uptime • App Errors • Successful Deploys
- 43. ©2008–19 New Relic,Inc. All rights reserved KEEPING YOUR MODERN APPLICATION RUNNING 43 Dynamic Infrastructure Managing Risk Instrument All the Things DevOps Culture
- 44. ©2008–19 New Relic,Inc. All rights reserved Customers demand modern applications Modern applications modern technologyrequire Keeping Your Application Modern Modern monitoringModern infrastructure Modern processes and procedures
- 45. ©2008–19 New Relic,Inc. All rights reserved I hope, I hope, I hope… 45 ...the site stays up!
- 46. ©2008–18 New Relic,Inc. All rights reserved
- 47. ©2008–18 New Relic,Inc. All rights reserved Modern Applications Require… 47 Ops …modern processes… …modern teams… Modern Enterprise
- 48. ©2008–19 New Relic,Inc. All rights reserved THANK YOU Lee Atchison Senior Director Strategic Architecture at New Relic Inc. @leeatchison leeatchison 48 Architecting for Scale By: Lee Atchison Published by: O’Reilly Media http://scalinginthe.cloud “#1, Top DevOps Books to read in 2018” – Apiumhub “10 Tech Books for Summer Reading” – Information Week/Network Computing
Editor's Notes
- #3 Hello! I hope you all have had a great day today. We’ve talked a lot about a lot of varied topics. Great customer talks, great talks from New Relic experts. All of this telling you about how New Relic can be used to help you manage your business applications.
- #5 Your applications…that’s the key. You work for a company that has applications that you build and manage. They are critical to your business. Applications that scale…applications that must stay operational.
- #6 You have big days. Days that are critical to the success of your company. Whether it’s the day of a new product launch, Black Friday, election day. {c}Whatever day it is, it’s your biggest day of the year. {c}It’s the day that your company will either make it…or break it.
- #7 You must manage your application to scale to your biggest day, and your biggest day grows and grows every year. Your application needs grow and grow…and ebb and flow…and spike…and have unpredictable needs.
- #8 Your company is dependent on your application working. Your customers *ASSUME* your application will work. Your customers will not tolerate outages.
- #9 When your customers are expecting your application to function…
- #10 An outage is not acceptable… It disappoints your customers… and disappointed customers, disappear. Or go to your competitors.
- #11 Your applications must be maintained…they must scale…they must maintain availability. They must function…all the time.
- #12 You know, my son has an application that he has to use to get some of his medical benefits. It’s a government application. When you launch it, it says it only works {c} between the hours of 9-5, Monday-Friday, Eastern Time. You try and use it any other time of the day or night…or weekends…it just doesn’t work. How many of you can get away with an application functioning like that.
- #13 No, our applications must work, and they must work all the time, and they must work no matter how many customers want to use it at the same time. {c} Bottom line, our applications…must be modern. Modern application development, delivery, and management processes are essential in order to build applications that keep our customers happy. To meet our growing digital needs, and to keep our front doors open.
- #14 Building a modern application requires a team. A cross functional team from all across your company, in order to build your application and keep it functioning. In order to build and manage a *modern* application.
- #15 And to do their job, these teams have to ask important questions… Important questions, such as Am I open for business? Are my customers engaging? How am I doing financially?
- #16 Every step in the product development, deployment, and operation process requires answers to important questions. And you must all work together to answer those questions. In short, building a modern application, or modernizing an existing application, requires tools and techniques. Processes and procedures.
- #17 What does it take to keep your modern application running, and keep it…well…modern? I believe there are four critical tools and processes needed to keep modern applications running. I want to talk about each of these four in turn.
- #18 First, our modern applications must be highly dynamic, which requires a highly dynamic infrastructure.
- #19 In the old days, applications ran in static data centers. All the systems were well defined, the interfaces were controlled, managed, and easy to understand. Your operations team knew exactly what it took to keep the systems running. Simply looking at the servers, waiting for deviations or variations in performance, was good enough. Deviations or variations in performance indicated a problem. It was that simple…
- #20 But in the new world. Our applications are much more dynamic. They are more sophisticated, and serve a more sophisticated customer. Our static data centers simply don’t meet our needs anymore. We are out growing them.
- #21 In the new world, resources are created dynamically. The cloud allows us to request and consume resources on demand. The world of the operations team can no longer be as simple as tracking resources on a spreadsheet. The resources they are responsible for are dynamic and transient. Their world has gotten a lot more complicated.
- #22 Building dynamic infrastructures in the cloud allows you to {c} scale your applications better. {c} It also allows you to make changes to your application faster and easier. {c} Both of these ultimately result in higher availability…and greater value from your applications. Dynamic infrastructures are critical to building modern applications… {c} The way you’ve built things in the past, just won’t work in the future…
- #23 The next key is managing risk. Managing risk is not as easy as it use to be. Risk is much more complex and much more pervasive in modern applications, and requires modern techniques to manage.
- #24 Let me give you a real life example of risk management gone bad… This is an overheard conversation. A report, by an operations engineer. I want you to see if you hear anything familiar in this conversation…
- #25 We were wondering how changing a setting on our MySQL database might impact our performance…
- #26 … but we were worried that the change may cause our production database to fail…
- #27 … Since we didn’t want to bring down production, we decided to make the change to our backup (replica) database instead…
- #28 … After all, it wasn’t being used for anything at the moment.
- #29 Of course, that’s when the random act of nature occurs…and we remember why we had a backup database. We remember why the backup was needed...
- #30 This problem is the result of bad planning. It’s the result of bad decision making. It’s the result of not understanding the stresses your application is on. And it is the result of not understanding the inherent risk in performing such an operation. Understanding and managing risk is core to keeping modern applications running at scale.
- #31 All systems have risk in them There is risk that a server will crash There is risk that a database will get corrupted There is risk of network problems… There is risk of software failing Risk is a measure of the likelihood of a surprise occurring
- #32 On the surface, keeping a system available requires removing risk…which means removing surprises. {c} But as systems become more and more complicated, this becomes less and less possible. {c} Removing risk is not a viable option.
- #33 Living with risk in a large highly available application is about: {c} Managing what your risk is {c} Managing how much risk is acceptable {c} Knowing what you can do to mitigate the risk {c} We call this risk ***management*** Risk management is at the heart of building every highly available systems. {c} Risk management is not about removing risk, it’s about understanding & mitigating risk
- #34 The third key to modern application development and operation is building and maintaining a DevOps culture.
- #35 So, let’s talk about what DevOps is, but we’ll start by talking about what it is not… Dev Ops is not a change to your product or how the product is made {c} Dev Ops is not simply a process or procedural change {c} And DevOps is not something you “migrate to” or “institute”…
- #36 DevOps is nothing short of a …{c}…cultural transformation It’s a change to your entire organization. It’s a change to how your organization thinks, and behaves. It is a core flush of the inside out of how your organization works and builds modern applications
- #37 DevOps changes: How your organization develops, deploys, and monitors applications. And how it responds to problems when they occur. {c}DevOps is all about ownership and maintaining ownership at the individual team level.
- #38 In order to build ownership at the team level, you must build tooling that allows your teams to facilitate their ownership. I believe this cannot be done, without also embracing dynamic infrastructure and the dynamic cloud {c} In other words, Adopting DevOps means adopting the Cloud {c} And Adopting the cloud means Adopting DevOps They are mutually symbiotic They go together They are integrated concepts {c} You cannot succeed with one without embracing the other
- #39 Last but not least in keeping modern applications running is instrumentation and monitoring.
- #40 Problems can come from anywhere… Continuous monitoring using built in instrumentation allows you to: {c} Anticipate and predict problems *before* they happen. In other words, analyze trends and understand when those trends go sideways. {c} Notice when a problem occurs and acknowledge that problem. This is alerting. This is having your monitoring inform you when there is something worthy of you paying attention to. {c} And third, once a problem is identified, monitoring is critical in diagnosing and resolving that problem. It allows you to determine easily and quickly what is causing a problem and allows you to correct it. {c} Reducing Mean Time To Detection and Mean Time to Resolution are critical measures that allow you to keep your modern applications running and highly available.
- #41 If you don’t have visibility into your application, and have access to the data you need at the time you need it. You’ll: 1) Waste time fire fighting…because you won’t know where the problem is… 2) Meaningless finger pointing across teams…one team won’t trust another team that is telling them the problem is in their service…without data 3) Lose money…you don’t make money when your application is not available 4) Make customers unhappy… 5) Unhappy customers tell other people…
- #42 You also need the right data. You need to know how your application is performing, to answer questions as simple as, “Am I actually open for business?”. But you also want to know how easy it is for your customers to make use of your application. What is their experience? And you need to know how your business is doing. You need to monitor the right components…and you need to monitor the right data. Success involves all three types of analytics. Is the software working? Is it meeting the customer’s needs? Is it meeting your business needs? All of these three things are interconnected.
- #43 This is the measurement framework. {c}{c}{c}{c}All aspects of this framework are important to your overall business success. By combining data from all these sources, teams can find out how their concerns are impacted by other teams.
- #44 That’s it. That’s the four keys to building and operating a modern application to meet the modern needs of our customers today. Dynamic infrastructure, managing risk, DevOps culture, and instrumentation. These are four critical tools and processes for keeping modern applications running.
- #45 Our Customers demand modern applications. {c} And modern applications require…modern technology {c} Modern technology means modern infrastructure, modern processes and procedures, and modern monitoring.
- #46 It is no longer sufficient to simply sit back and hope your application stays operational.
- #47 Because avoiding this is critical to every modern business and every modern application.
- #48 Keeping applications running involves: Creating and using modern processes. {c}Creating and maintaining modern teams. {c}In short, creating the modern enterprise
- #49 Thank you