New Relic After Lift and Shift - FutureStack 2019
•Download as PPTX, PDF•
0 likes•105 views
After Lift & Shift, a continuous application modernization strategy is the key to successfully growing your business in the cloud.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to New Relic After Lift and Shift - FutureStack 2019
Similar to New Relic After Lift and Shift - FutureStack 2019 (20)
Recently uploaded
Recently uploaded (20)
New Relic After Lift and Shift - FutureStack 2019
- 1. ©2008–19 New Relic, Inc. All rights reserved©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK
- 2. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK 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.
- 3. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK AFTER LIFT & SHIFT WHAT DOES SUCCESSFUL MODERNIZATION TAKE? bit.ly/NewRelicAfterLiftShift
- 4. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK KEVIN DOWNS Principal Cloud Strategist @kupsand linkedin.com/in/kevin-downs
- 5. #FUTURESTACK ©2008–19 New Relic, Inc. All rights reserved #FUTURESTACK
- 6. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Agenda The cloud is just the beginning Reasons to modernize Modernization options & risk 1 2 3 4 Continuous application modernization
- 7. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK 75% Retire Retain Repurchase Rehost Replatform Refactor
- 8. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Modernization Strategies 75% Rehost Replatform Refactor
- 9. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Rehost / Replatform / Refactor Modernization Strategies Exploit Best Execution Venues Source: 451 Research’s Voice of the Enterprise: Digital Plus, Workloads & Key Projects 2019 Q: Which of the following best describes your organization’s overall IT infrastructure approach to mission-critical legacy applications and workloads going forward? Repurchase and shift. Replace current on-premises applications with SaaS or off-premises hosted versions of the applications. 34% 9% 17% 16% 24% Modernize (Replatform). Retain existing applications on-premises but move to more modern applications and infrastructure architectures. Lift and shift (Rehost). Migrate existing on-premises applications to off-premises/cloud environments with minimal changes to the application code or business logic. Retain. Keep current applications unchanged on existing on- premises infrastructure. Refactor and shift. Re-architect/redesign existing applications using cloud-native frameworks and deploy in off-premises cloud environments.
- 10. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK SOMETIMES, I TELL THE TEAM TO JUST MOVE IT. Jim Scholefield - Nike’s Global CIO ©2008–19 New Relic, Inc. All rights reserved
- 11. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Lift & Shift Benefits Cost Infrastructure Development
- 12. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Proved Success
- 13. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK JOSH BIGGLEY Senior Engineer, Infrastructure Applications Cardinal Health @jbiggley linkedin.com/in/jbiggley
- 14. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK
- 15. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK JAVIER MIGUEZ Director, Technology Operations Fleet Complete linkedin.com/in/javier-miguez
- 16. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK What’s Next? Ideas Cost SavingsImprovements
- 17. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK 97% COST REDUCTION FOR JUST ONE APPLICATION. Mitch Shue - Morningstar CTO ©2008–19 New Relic, Inc. All rights reserved
- 18. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Why Modernize? Elasticity Ease of deployment and management Resiliency Flexibility that the cloud offers
- 19. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK How & What Understand your modernization options Deep insight into your applications
- 20. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Modernization Options and Risk Refactor Replatform Rehost Retire - Retain - Repurchase Risk
- 21. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Risk Dependencies Automation Customer Experience Unexpected Errors Incompatibility Extensive Changes Expected Outcomes
- 22. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK CONTINUOUS APPLICATION MODERNIZATION
- 23. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Continuous Application Modernization Goals Understanding Approach Observability Repeat 1 2 3 4 5
- 24. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Side note Modernization & DevOps
- 25. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Step One: Goals Example Goal Increase revenue1 Respond faster to business Optimize IT costs Improve quality & performance Outpace competitors Drive revenue Reduce service costs Improve customer satisfaction Increase customer base IT Impact & KPIs Business Impact & KPIs Improve profitability2 Improve customer experience3 Grow market share4
- 26. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK KPIs - Business and Technical Corporate KPIs • Perceived Load Time • Apdex • Error % • Mobile Crash Rate • Route Searches • Segments • Check Ins • Fare Class • Promotions • Point Redemptions • Complementary Services • Travel Packages • Loyalty Program Application / Infra • Apdex • Availability • Throughput • App/API/DB Response Times • Error % • Memory Footprint • CPU Workload • Disk Workload • Network Throughput DevOps • Builds • Commits • Deploys • Defects Web • Session Count • Session Duration • Page Views • DOM Readiness • Page Render • Perceived Load Time • Error % • Apdex Trends • Active Users • Response Times • Session Durations Mobile • App Launches • User Counts • Load Time • Response Time • Crash Rates • Crash Locations • Error Rates (HTTP, Network) • API Errors • Session Duration Support • Support Incidents • MTTI • MTTR • Cost per Incident Sample KPI Facets • Geography • XYZ Business Unit • XYZ Product • Device Type • OS Type • Mobile Platform • Carrier • Website Name • Page Name • Browser Type • Error Type • Application Name • Cloud Provider • Host • Success/Fail Reason
- 27. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Step Two: Understanding Application Infrastructure Application Quality & Performance Impact on the Business
- 28. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Step Three: Modernization Approach Refactor Replatform Rehost
- 29. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Common to All Understand risks and how to minimize them Use an informed approach Compatibility analysis Deep understanding of your components Use data before, during, and after
- 30. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Replatforming - Reasons Scalability Reliability & performance Costs
- 31. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Informed Replatforming End-user experience Application performance Application dependencies Application issues Resource usage Existing components
- 32. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Discover Application Components
- 33. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Refactoring - Reasons Revenue Customer experience New features
- 34. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Informed Refactoring Changes Issues Infrastructure Working - errors - slow Deployment speed Business KPIs
- 35. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Types of Refactoring Improving code Deployment model Technology refactoring
- 36. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Find the Bottleneck
- 37. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Step Four: Observability Before During After Evaluate Plan Modernize Optimize
- 38. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Cost Optimization Reduced mobile data transfer by 87%, helping improve user experience Reduced errors by 95% within two-month timeframe Accelerated release cycles from as long as 12 weeks to mere hours “We were forecasting to come in significantly over AWS budget by the end of the year. Within two weeks, we analyzed our systems and applications, identified key areas that could be addressed quickly, and ended up coming in 1% under budget by the end of our financial year. This would have been much harder without new relic, which we used to gather data across our platform, instances, and applications, providing visibility and ownership to right-size our environment. David Stanley, Director of Reliability
- 39. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Step Five: Rinse and…
- 40. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK Summary The cloud is just the beginning Reasons to modernize Modernization options & risk 1 2 3 4 Continuous application modernization
- 41. ©2008–19 New Relic, Inc. All rights reserved#FUTURESTACK THANK YOU Kevin Downs @kupsand linked.com/in/kevin-downs
Editor's Notes
- Over 20 years in industry 12 years as a Solutions Architect Infrastructure & Application Monitoring Had apps in both MacOS and iOS stores Specializing in: SaaS Cloud Adoption
- The cloud is just the beginning Lift & Shift has benefits There are a great number of reason to modernize Elasticity - Resiliency - deployment - management - flexibility Options are Rehost, Replatform, and Refactor - and Risk Dependencies - Automation - customers - Errors - Compatibility - Changes - Outcomes Continuous Application Modernization - 5 steps 5 steps: Goals - Understanding - Approach - Observability - Repeat Josh: Final thought? – democratization of data and observability Javier: Final thought?
- Pun intended
- Cost data center faster procurement/provisioning process Flexible payment models (Capex to Opex) Infrastructure better purposed instances Improved customer experience better operations management (OS patching upgrades etc) Disaster recovery Development Distributed development team New services available
- Maybe: On-prem to cloud website migration story We needed to move some apps to the cloud -- check We’re going all in with the cloud --- check We’re out of our data center(s) --- check Everything is as it should be --- ?
- Intro yourself What is your philosophy on moving to the cloud - lift & shift, replatform, refactor, etc? Josh: Speed of execution - velocity. Fast as possible
- Intro yourself What is your philosophy on moving to the cloud - lift & shift, replatform, refactor, etc? Josh: Speed of execution - velocity. Fast as possible
- Intro yourself What is your philosophy on moving to the cloud - lift & shift, replatform, refactor, etc? Javier: Going to modern. Hybrid - global - fast moving
- During your migration journey… You wanted to make more improvements You’ve learned a thing or two (or a hundred!) You want to increase cloud cost savings Basically, you want to modernize in the cloud ...and you know you need to!
- Your Goal: From the AWS Summit 2017 Chicago Lift and Shift to EC2, MS SQL & DynamoDB Modernized to an S3 Data Lake and AWS Lambda
- Take full advantage of… The question is not whether to modernize at all, but what and how to modernize. Should you move your core applications to the cloud? Which business areas or applications will deliver the largest impact or highest value for the business when modernized? Are there applications that should not be modernized because they have reached the end of their useful life? What are best practices for breaking monoliths apart?
- To answer these “what” and “how” questions about your legacy applications, you need two fundamental things: An understanding of your modernization options and Deep insight into your applications
- Failure to understand application dependencies, both externally and internally, and/or overly aggressive and complex project goals Lack of cost savings due to automation not being implemented or improved Negative impact on the customer experience due to poor performance or availability caused by unexpected errors Project time exceeds original plans because of unexpected errors and/or dependencies Failure to identify application incompatibility with the new platform. Extensive changes that require extended testing and debugging with dual infrastructures, temporarily driving up costs Failure to achieve expected business outcomes In any project, understanding the risks involved is the first step in minimizing them. While the risks for this type of modernization are relatively low, there are certain ones you may encounter when you replatform applications. These can include: These risks and others can be avoided or minimized by using best practices that are informed and guided by data derived before, during, and after the replatforming project.
- 5 Steps: Step 1: Set goals for the modernization. Step 2: Make sure you thoroughly understand each of your applications. Step 3: Choose the optimal modernization approach for each application. Step 4: Monitor and measure changes against your goals before, during, and after modernization. Step 5: Start over with step one.
- Before the break your went into DevOps... Modernization will allow for a company to adopt a high-performing software development environment. Application modernization enables DevOps success and vice versa. As legacy applications and their environments are modernized, DevOps teams can spend more time on developing and delivering new features and less on overcoming friction in the software lifecycle of existing systems. Josh: How does automation help your DevOps journey with modernization? → Small teams - pipelines - alert conditions Javier: How has modernizing of your infrastructure accelerated your delivery Cycles? → before to once-a-month to once-a-week - get to root cause
- Define and refine your goals Josh: During your journey, how did your focus change and how does Cardinal Health’s modernization impact that focus? → Customer Focused – essential to care Javier: One of your goals is uptime. Can you expand on this goal and how modernization helps that goal? → 99% to 99.8%
- The next step in the strategy is to get a clear understanding of each application and its interdependencies. To do this, take a baseline measurement that helps you figure out how each application currently performs. This gives you the foundation for making data-driven decisions as you create your initial roadmap for modernization. With this understanding, you can identify and prioritize applications to modernize and determine how you want to approach modernizing each application. Application Infrastructure How are resources being used? Which resources are being used by this application? What chronic resource issues exist (e.g., over- or underutilization)? Application Quality and Performance How is the application performing? What is normal, baseline performance? What errors does the application have currently? What are the application dependencies? How is the end user experience? Where is your application spending most of its time? Impact on the Business How does performance and reliability impact revenue? How much time do users spend on the application? How does the application impact conversion rates or order value? Do errors/downtime impact customer service costs?
- Now it’s time to use all the data you’ve gathered to make an informed decision about how to begin modernizing or further modernize each application. Although there are six industry-recognized approaches that you can consider, only the last three—rehost, replatform, and refactor—involve modernizing the application. We’ve already covered rehosting. Keep in mind that with an iterative modernization strategy, you can start with one approach, reap some initial benefits, and then continue to modernize through other approaches to obtain more benefits. For example, you could take a rehosted application and replatform it to swap out the current database for a cloud-based database service. Or, with a different, higher-priority application, you could decide to go straight to refactoring it to take advantage of additional cloud technologies.
- Improve scalability to accommodate business growth Improve reliability and performance for a better customer experience Reduce costs for software licensing and resource usage Reduce the total security surface area of your application Reduce the management efforts and associated time and costs Improve ability to make informed decisions
- Understand how apps and services in your architecture connect and talk to each other using Service Maps.
- Drive new revenue streams and/or optimize existing ones Create improvements that directly impact future revenue capabilities Deliver a better customer experience Enable faster time-to-market with new features Support a changing/new business model Comply with changing/new regulations
- What parts of the codebase change the most or have the most issues filed against them? These are potentially good candidates for making them a component (i.e. a microservice running in a container or AWS Lambda) Mitigate performance problems? Use serverless technologies? Use self-healing infrastructure and services rather than manage the infrastructure? Which parts of the codebase have (which indicates rework)? Stop self-managing infrastructure if it does not issues regularly reopened give you a competitive advantage? Which parts of the application perform well? Which parts are complex and prone to errors? Which parts take the longest to run? How well are deployments going? How fast are things provisioned? What are the key performance indicators (KPIs) that help you measure business impact?
- Going back to its traditional meaning, the first type of refactoring is all about improving an application’s code. The idea is to identify portions of the application where it makes the most sense to re-architect the code for quality, maintainability, performance, and predictability. It’s an opportunity to fix existing issues and create less complex and more streamlined code. After you’ve decided on the parts of the codebase to work on, the next step is to consider a newer deployment model. Choose the deployment model that makes the most sense for your organization based on your IT philosophy and future direction.
- Distributed tracing lets you see the path that a request takes as it travels through a distributed system. Use it to discover the latency of components along a path or understand which component is creating a bottleneck.
- It should now be clear that you need to fully understand how your applications perform before you can decide how and whether to modernize them. The baseline picture of application performance gives you data not only to inform your decisions but to serve as a comparison during and after your modernization effort. It also helps you identify any issues that you need to address before you begin the modernization. After the initial modernization iteration is complete, you can demonstrate success by comparing your previous baseline against current performance, customer experience, and business outcome data. Ideally, you’ll see improvements and identify areas where further modernization and optimization can help. Josh: Cardinal Health experienced an 11th hour hiccup, can you tell us about it and how New Relic was able to support you? → re: pivot to GCP – multi-cloud – co-locate (Dublin) Javier: How does New Relic keep everyone at Fleet Complete aware of what’s going on? → (Single pane of glass, bottlenecks, AWS Cost Explorer and NR)
- Forecasted to come in significantly over their cloud budget Trainline took two weeks to analyze their systems and applications to identify key areas that could be address quickly Ended coming in 1% under budget
- This last step is neither an actual step nor the last activity of the modernization process; rather, it’s a reminder that modernization is continuous, and that even as you gradually modernize your applications, there will always be new technologies and capabilities to incorporate and support. However, with each cycle of modernization, your organization is making significant strides in enabling and fostering digital transformation and the culture, process, and technology changes that must happen as part of it.
- The cloud is just the beginning Lift & Shift has benefits There are a great number of reason to modernize Elasticity - Resiliency - deployment - management - flexibility Options are Rehost, Replatform, and Refactor - and Risk Dependencies - Automation - customers - Errors - Compatibility - Changes - Outcomes Continuous Application Modernization - 5 steps 5 steps: Goals - Understanding - Approach - Observability - Repeat Josh: Final thought? – democratization of data and observability Javier: Final thought?