Migrating Legacy Applications to AWS Cloud: Strategies and Challenges
•Descargar como PPTX, PDF•
10 recomendaciones•4,191 vistas
To reduce the TCO of application infrastructure and to make them more scalable and resilient it is advisable to migrate on-premise legacy applications to AWS cloud. In this webinar, you will learn the benefits, key challenges and strategies to mitigate them. It will also talk about leveraging the cloud infrastructure to further modernize the application. Key Take Away: Opportunities and challenges while migrating premise application to cloud. Identifying the applications Assessing cloud architecture and costs Data migrations strategies and options Strategies for migration applications Leveraging the cloud and optimization
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (20)
Similar a Migrating Legacy Applications to AWS Cloud: Strategies and Challenges
Similar a Migrating Legacy Applications to AWS Cloud: Strategies and Challenges (20)
Más de OSSCube
Más de OSSCube (20)
Último
Último (20)
Migrating Legacy Applications to AWS Cloud: Strategies and Challenges
- 1. Migrating Legacy Applications to AWS Cloud: Strategies and Challenges by Ram Awadh Prasad
- 3. Who Are We • Global Solutions Provider having offices in the US, UK and India. • We offer complete solutions in the domain of Digital Transformation, IT Modernization and IoT. • Appraised at CMMI Level 3, we've been amongst the top 100 Great Places to Work® for three consecutive (2014, 2015 & 2016) years. • We’ve delivered enterprise solutions to the likes of The New York Times, PVR Cinemas, ACER, Intel, CU Solutions, among others.
- 4. Digital Transformation Practice • PIM (Product Information Management) • WCM (Web Content Management) • DAM (Digital Asset Management) • e-Commerce Modernization Practice • Cloud • Enterprise Mobility • Application Modernization IOT Practice • SMART Track & Trace • Product Lifecycle Management • Big Data - Analytics © 2015 OSSCube LLC. All rights reserved. What We Do
- 5. Overview & Key Takeaway • How Cloud Computing is changing the business paradigms. • What are the opportunities and benefits of cloud computing? • Why migrating legacy applications to cloud is a challenge? • How to go with migration of these applications? • How to leverage cloud services to enhance your
- 6. Cloud Computing – Changing how businesses operate
- 7. Cloud is not just a Technology Shift • Cloud Computing is one of the newest technological developments to shake up the business world • However, it’s not just an advance in technology • It represents transformation for an entire organization › People, › Processes, and › Systems. • Transforming business models and efficiencies at enormous speed
- 8. Cloud Computing is growing at an enormous rate
- 9. Cloud Computing is growing at an enormous rate 16.5 % projected growth in Public Cloud Services in 2016 from 2015 38.4 % will come from cloud system infrastructure services 3.5 fold load increase in Cloud Data centers 86 % workloads will be processed by cloud data centers by 2019 Gartner reports "Forecast: Public Cloud Services, Worldwide, 2013- 2019, 4Q15 Update“ Cisco Global Cloud Index: Forecast and Methodology, 2014–2019
- 10. What is fuelling this rapid growth? • Reduced infrastructure costs • Reduced time to market • Always on availability • Increased business agility • Virtually unlimited scalability and storage • On-demand provisioning and automation • Flexible choice of programming models, languages, operating systems • Infrastructure and Process Automation
- 11. Migrating Legacy Applications to the Cloud
- 12. Why migrate legacy applications? • Changing business needs – rising need for elasticity, scalability, global access • Longer time to market new services and features • Complex and Less agile hence difficult to make changes • High cost of maintenance and routine updates • Difficult to integrate with modern applications • Difficult to upgrade • Business continuity and difficulty in disaster recovery
- 13. Challenges moving Legacy Applications Applic ation Archite cture Challenges and Concerns
- 14. Migrating your Apps – A Phased Approach
- 15. Phased Approach to Cloud Migration Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the cloud
- 16. Perform Assessment Assess Applications and Workloads Security and Compliance Assessment Financial Assessment – Build the Business Case Develop Migration Plan Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud
- 17. Assessment - Applications and Workloads • Identify candidate applications based on architecture and strategic considerations: › Which applications can be moved to the cloud › Define order or priority in which applications would be moved › Which applications should remain in-house. › Do we need to run some applications in hybrid Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud
- 18. Assess Applications and Workloads Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud Business Considerations Lifecycle Considerations Architecture Considerations Data Considerations Technology Considerations Security Considerations Integration Considerations Assessing Applications - Key Considerations
- 19. Identifying the Right “Candidate” for the Cloud • Applications with minimum upward and downward dependencies. • Applications with underutilized assets • Applications that have an immediate business need to scale • Applications that have architectural flexibility • Applications that utilize traditional tape drives to backup data • Applications that require global scale • Applications that are primarily used by partners. Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud
- 20. Licensing options on AWS Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud • Oracle • Sybase • Adobe • MySQL etc.. Bring Your Own License (BYOL) • RedHat • Novell • IBM • Wowza etc. Utility Pricing Model • ISV SaaS-based Providers ISV SaaS-based Cloud Service
- 21. Security and Compliance Assessment • Overall risk tolerance • Confidentiality, integrity, availability, and durability • Regulatory or contractual obligations • Security threats • Intellectual property protection and legal issues • Options for data retrieval • Comfort level with shared infrastructure services Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud
- 22. Build the Business Case Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud Cost Analysis • Thorough cost analysis of the application on premise vs overall cost of application migration and cloud infrastructure Service Levels • Ensure that the level of service provided by the cloud-based application will be comparable to or better current service levels Business Impact • Additional business factors like revenue impact, customer engagement, user satisfaction
- 23. Cost Analysis – On Premise Costs vs Cloud Costs • Perform comprehensive cost analysis • Use TCO methodology • Consider all direct / indirect costs • Quantify the indirect economic value of cloud features. Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud HW, SW and Network etc. On-going service Service management Application re-designs, deployment and testing Application maintenance and administration Application integration. Training and Cloud skills Costs to Consider
- 24. Service Levels Assess how level of service provided by the cloud-based application compare to current service levels: • Application availability • Application performance • Application security • Privacy • Regulatory compliance Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud
- 25. Business Impact Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud Revenue impact Customer acquisition or engagement impact How will it impact user satisfaction Time to market improvements Cost of handling peak loads Business Impact
- 26. Develop a Technical Plan Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud Service Model – IaaS or PaaS Application Migration Data Migration Security Integration Monitoring Management Scalability Availability and Backup
- 27. Data Migration Plan – Key Considerations • Different storage options available on AWS • Different RDBMS (commercial and open source) or NoSQL options • Data segmentation strategy and trade- offs • Tools and effort needed to migrate all my data. • Make the right tradeoffs among various dimensions Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud Cost, durability, query-ability, availability Latency, performance (response time) Relational (SQL joins), unstructured data, size of object stored (large, small) Accessibility, read heavy vs. write heavy, update frequency Cache-ability, consistency (strict, eventual) and transience (short-lived) Tradeoffs to consider
- 28. Data Migration Plan – Options on the AWS Cloud Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud Fileserver Systems, Backups and Tape Drives • Amazon EBS • Amazon S3 • Amazon Glacier • Amazon EFS Relational Databases • Amazon RDS (Supported DBs) • Relational DB AMIs (Other DBs) No SQL Databases • Amazon Dynamo DB Data Migration to AWS • Amazon Import/Export Service • Amazon Direct Connect • Amazon Storage Gateway
- 29. Application Migration - Strategies Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud Forklift Migration Strategy Hybrid Migration Strategy • Forklift or “pick it all up at once” approach • Suited for self-contained applications e.g. Web applications, backup/archival systems • Essentially, swapping real physical servers with EC2 instances • Minor code changes and configuration needed • May not be able to take immediate advantage of the elasticity • Moving only some parts of an application to the cloud while remaining on premise. • Need to take care of coupling and integration challenges.
- 30. Address Security Concerns • Identify data / code to be protected • Map data to security classification • Identify which information raises privacy concerns • Examine applicable regulations • Perform risk assessment of violations and impact on business • Review the cloud providers’ security/privacy measures • Design how to authenticate and authorize users Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud
- 31. Perform Migration Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud Deploy the Cloud Environment • Compute • Storage • Network • Security Install and Configure the Applications • Applications • Middleware • Integration bridges Harden the Production Environment • Security and Access • Backup and DR Execute a Mock Migration • Migrate pilot date • Run functional tests • Test integration • Verify access and security Cutover to Production Cloud • Final Data Migration • Transfer Users • Transfer Operations
- 32. Perform Migration – Harden your application AWS credentials • Regularly rotate your AWS access credentials • Multi-factor authentication AWS resources • AWS users, groups, roles and policies • Revisit and monitor IAM user policies • Security groups in Amazon EC2 Protect your data • Encrypting it at-rest (AES) • In-transit (SSL) Automate security policies • Instance Profiles • Cloud formation templates Backup and DR • Multi AZ Deployment • Cross region replication Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud
- 33. Leveraging the Cloud Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud Leverage other AWS services • Amazon CDN • Amazon SQS • Amazon SNS • Amazon SWF Automate elasticity and SDLC • Auto scaling • Code Commit, Code Deploy, Elastic Bean Stalk Content Delivery • S3 Static Website • Amazon could front Leverage multiple availability zones • Multi AZ Deployment • Multi AZ RDS, Replication
- 34. Leverage the Cloud - Optimization • Understand Usage Patterns • Optimize usage based on demand • Implement advanced monitoring and telemetry • Monitor and automatically terminate the underutilized Instances • Leverage Amazon EC2 Reserved Instances • Track your AWS Usage and Logs • Enhance Security of Your Applications • Re-engineer your application Perform Cloud Assessment Develop Technical Plan Address Security Concerns Perform Migration Leverage the Cloud
- 35. Summary • You can reap the benefits by moving your legacy applications to the cloud. • Just moving the application to cloud does not make if more cost effective or efficient. • Moving legacy applications to the cloud can be challenging and not all applications can be moved to the cloud. • A well planned and phased migration is the key to successful migration • You can leverage AWS advanced services and features to optimize your applications on the cloud further.
- 36. Thanks ! For queries please write to ram.awadh@osscube.com Q & A
Notas del editor
- Thank you for the great introduction- xyz (presenter's name). Hello everyone! Hope you're doing well. Welcome to the Our Webinar.
- Before we begin with today’s topic, let me very briefly walk you through the background of OSSCube.
- We're a Global Solutions Provider headquartered in the US, having offices in UK and India. We offer complete solutions in the domain of Digital Transformation, IT Modernization and Internet of Things. In the space of IoT, we're extensively working on creating certain IP's, about which you'll probably hear soon. OSSCube has been amongst the top 100 Great Places to Work® for three consecutive years from 2014 to 2016; it was included in NASSCOM's top 5 places to work in 2015. And in this year, OSSCube has bagged the India Emerging 20 award and has been named one of India SME 100 Award winners. Some of our prestigious clients include, The New York Times, ACER, PVR Cinemas, CU Solutions, Intel, MakeMyTrip, GoGo and many more.
- Our Digital Transformation Practice focuses on improving digital customer experience using best of breed Product Information Management, Web Content Management, Digital Asset Management and e-Commerce solutions. Our IT Modernization Practice offers a complete range of solutions around Cloud, Enterprise Mobility, Application Modernization. And our IoT Practice comprises of SMART Track & Trace, Product Lifecycle Management and Big Data-Analytics solutions. We are partners with AWS, Talend, MariaDB, SugarCRM, Magento, Drupal. OSSCube is also the world's one and only Zend Centre of Excellence and an exclusive partner of PIMCORE in North America. That, pretty much sums up about OSSCube. Let's proceed with today's topic.
- Lets have a quick peek into how Cloud Computing, especially public cloud computing is growing at enormous rate. This is a kind of revolution and business cannot afford to be left out of this revolution.
- Cloud Computing is one of the newest technological developments to shake up the business world. However, it is not just about an advanced technology. It is about a paradigm shift, that is changing how businesses operate. It is transforming and redefining how businesses provision and manage IT resources. At the same time it is also transforming the people, processes and systems. It is introducing new business modules and transforming the existing models and efficiencies at enormous speeds.
- Trends and projections on Public Cloud Computing spending from 2015 to 2026,
- Some quick figures from Gartner report and Cisco Global Cloud Index, tells the same story. Lets take a brief look at the factors that are fueling the rapid expansion of cloud services.
- Reducing infrastructure costs due to improvements in technology including compute power, storage, internet bandwidth etc. Virtualization of compute, memory and storage. Time needed for provisioning resources – from months to minutes, multiple channels 8-5 availability replaced by 24X7 availability… Different platforms, Operating Systems, AMIs, Compute and Storage options and host of other services. Automated provisioning, automatic and continuous deployments, always on monitoring and almost real time reporting
- Changing business needs: Many legacy applications built years back are not able to meet the changing business needs of elasticity, scalability etc. Longer time to market: It takes longer to roll out new services and features to support business expansion. Complex and Less agile: Architecture of these applications makes it difficult to make changes to the application.. Not to mention making compatible with newer applications. Cost of maintenance: Expensive maintenance and routine updates. Difficult to integrate: As standards are evolving and new standards being developed, integrating with these modern standards based applications is difficult Difficult to upgrade: Legacy applications - especially client server applications require client software to be installed on desktop computer – are difficult to upgrade. Business continuity and disaster recovery – Costly setups for DR, Remote DR centers, Old and time-taking methods of backup / restore.
- Application architecture – Hardware / SW compatibility, distributed nature of cloud, latency issues Integration and tight coupling with other applications – The applications are generally developed in house, in phases and tightly coupled with other applications. Challenges of data migration and integration – Data sources, non standard formats, volume of data Licensing and support issues – Licensing may not be supported on the cloud, support contracts may not be valid and need to be written Security of sensitive data – pushing propriety sensitive data to cloud, financial / legal implications of data loss or breach. Fear of loss of control – since the application as well as data is moving out to the cloud. Cloud service provider lock-in
- Assess Applications and Workloads
- Business Considerations – How critical is the application to the business, who are the end users Application Lifecycle Considerations – Still under development? Awaiting a refresh? About to retire? Application Architecture Considerations – Will application architecture work on the cloud? If not, how much changes will be needed? What are the dependencies?... Data Considerations – Data source, privacy, volume of data etc. Technology Considerations – Hardware and Software compatibility, Security Considerations Integration Considerations – Integration with on premise applications?
- Services or components that have minimum upward and downward dependencies. E.g. backup systems, batch processing applications, log processing systems, development, testing and build Applications with under-utilized assets; Applications that have an immediate business need to scale and are running out of capacity; Applications that have architectural flexibility; Applications that utilize traditional tape drives to backup data; Applications that require global scale (for example, customer-facing marketing and advertising apps); or Applications that are primarily used by partners
- Bring Your Own License (BYOL) – Applicable to vendors who support cloud deployment Oracle, Sybase, Adobe, MySQL, JBOSS, IBM and Microsoft etc, Use a Utility Pricing Model with a Support Package – Vendors who have partnered with AWS for utility model licensing RedHat, Novell, IBM, Wowza offer pay-as-you-go licenses etc. Use an ISV SaaS-based Cloud Service
- Overall risk tolerance? Are there various classifications of my data that result in higher or lower tolerance to exposure? Main concerns around confidentiality, integrity, availability, and durability of my data? Regulatory or contractual obligations to store data in specific jurisdictions? Security threats? What is a likelihood of those threats materializing into actual attacks? Intellectual property protection and legal issues of my application and data? Options if I decide that I need to retrieve all of my data back from the cloud? Internal organizational issues and comfort level with using shared infrastructure services?
- Not just hardware expense + compute and storage resources etc. Consider other direct / indirect costs for a valid comparison between the two alternatives. On-going service costs. Service management, license management Application re-designs, deployment and testing. Application maintenance and administration. Application integration. Cost of developing cloud skills. Use TCO methodology - compare the total cost of owning, operating, and maintaining IT infrastructure with Cloud costs. Conduct a separate analysis to quantify the indirect economic value of cloud features.
- Application availability: The criticality of the application to business operations will determine the availability requirements that must be clearly specified in the cloud SLA. Application performance: Will the desired application performance be achievable with the cloud service? Application security: How is application security impacted by moving to cloud? What are the security controls and if they are operating effectively. Privacy: Personally Identifiable Information (PII) handled by a cloud-based application must be properly stored and maintained. Access to PII stored in a cloud service must be restricted as required, including from cloud service provider personnel. Regulatory compliance. Government and industry regulations may require additional measures, such as restricting the migrated applications and data to reside in a specific geographic region.
- Revenue impact. If the application is used to generate revenue, is the move to cloud computing expected to increase that revenue? Customer acquisition or engagement impact. User satisfaction. Does one expect an improvement in availability or response times that will result in increased user satisfaction? Time to market improvements. Will the move to cloud computing shorten the time it takes to deliver functional enhancements to end users? Cost of handling peak loads. The cost of scaling server capacity up and down to match spikes in demand for the cloud-based application should be compared with similar costs before migration.
- Skills: Skills necessary to prepare and migrate the application components. Security: Includes access to the application, user authentication and access, data encryption during transition and at rest. Integration: Integration with other applications and services within the customer organization, new authentication methods, and other technical changes to avoid network latency and throughput issues. Monitoring and Management: The monitoring and management of the application running in the cloud service must be considered. Scalability: Applications have to be structured appropriately to take advantage of scalable cloud resources, and this may require changes to the application code. Availability and Backup: In-house designs to support the availability of the application may need significant adaptation to deal with the cloud service environment, especially for PaaS services.
- The hybrid migration strategy can be a low-risk approach to migration of applications to the cloud. Application moved to cloud in parts one at a time. Need to build Web Service channels for communication between application components on premise and those on the cloud. Forklift Migration Strategy forklift or “pick it all up at once” and move it to the cloud Suited for Self-contained Web applications that can be treated as single components and backup/archival systems Major effort on minor code changes and configuration might not be able to take immediate advantage of the elasticity and scalability of the cloud because, after all, you are swapping real physical servers with EC2 instances Hybrid Migration Strategy A hybrid migration consists of taking some parts of an application and moving them to the cloud while leaving other parts of the application in place.
- Understand exactly what data (including what code, since code may be the confidential asset to protect) will be migrated to the cloud service. Map this data to your security classification e.g. clear text, encrypted etc. Identify sensitive information e.g. account numbers, dates of birth, addresses, etc. Examine applicable regulations (especially in the finance and health domains) and determine what needs to be done to meet these regulations, and whether it is possible to meet these demands while migrating to cloud computing. Perform the normal risk management tasks of assessing the risk of security or privacy violations, and the impact on the business. Review the cloud providers’ security/privacy measures (including physical security, personnel screening, incident notifications, etc., not just the technical security protection measures), and make sure that they are documented in the cloud SLA. Design how to authenticate and authorize users.
- Deploy the Cloud Environment. Provision, install and test the necessary storage, compute, network and security resources that constitute the cloud environment in which the migrated application will run. Install and Configure the Applications. The applications and supporting middleware should now be installed and configured on the cloud servers. Cloud service providers frequently do this through automated deployment of templates. Harden the Production Environment. Install additional utilities for business continuity and security. Note that some of these services may be provided by the cloud service provider, in which case they do not need to be installed, but they should still be tested. Execute a Mock Migration. Undergo a trial run of the migration project plan to uncover unintended results or unnoticed issues during the planning phase. The mock migration date should be sufficiently distant from the desired final cutover date to have time to rectify problems. Involve the cloud service provider in the migration date selection. Cutover to Production Cloud. Assuming a successful mock migration, or one that only encountered minor issues with a clear fix, establish a formal cutover schedule. If the mock migration ran into serious issues, then it needs to be repeated after correcting the causes.
- Now that I have migrated existing applications, what else can I do in order to leverage the elasticity and scalability benefits that the cloud promises? What do I need to do differently in order to implement elasticity in my applications? How can I take advantage of some of the other advanced AWS features and services? How can I automate processes so it is easier to maintain and manage my applications in the cloud? What do I need to do specifically in my cloud application so that it can restore itself back to original state in an event of failure (hardware or software)?