6rs Of Migration Aws Reinvent 5u2a6g
This document was ed by and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this report form. Report 3i3n4
Overview 26281t
& View 6rs Of Migration Aws Reinvent as PDF for free.
More details 6y5l6z
- Words: 2,493
- Pages: 38
Identifying Your Migration Options: The 6 Rs Nirav Kothari, Principal Consultant AWS Professional Services Jeffrey Gelb, Head of Foundational Engineering Scholastic Inc. November 30, 2016 © 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Agenda In this session, we will cover: • The 6 Rs of migration • Assessment-based approach • Considerations when selecting the various Rs • Discuss each R of migration strategy • How Scholastic leveraged the 6 Rs
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
6 Rs migration strategy • Customers will keep host/application in their source environment • Minimal analysis/validation of scope and application affinity • Dependency on integrating service management
1
Retain (Revisit) • Application and host decommission on source • No migration to target • Application owner approvals needed
2
Retire 3
Rehost
4
• Up-version of the OS and/or database onto the target cloud • Some level of application changes • Application reinstallation on the target • Database to Amazon RDS
Replatform 5
• OS and/or database porting • Middleware and application change to cloud service offering • Data conversion; Database transition to MySQL, Amazon Aurora, or other
Refactor • Like for like application migration to target cloud • Minimal effort to make the application work on the target cloud infrastructure (minimal application layout change) • Storage migration will be needed (without conversion)
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
6
• Application architecture changes may also require Up-version or Porting • Use SaaS-based offerings, application architecture changes may require porting • Middleware, data modernization; application consolidation/stacking
Rearchitect (Replace)
Assessment-based approach • Financial assessment • Security assessment • Compliance and regulatory assessment • Business assessment • Technical assessment • Contractual assessment
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Application considerations • • • • •
What is the application roap? What are the costs associated with this application? What improvement options are available to enhance service? Are there any risks of not making changes to this application? Where does this application align with the technology goals of the organization?
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Mapping drivers to migration strategy High
Rearchitect (Replace)
Business Agility/Value
Refactor Replatform Rehost
Retain (Revisit) Retire
Low
Migration Effort
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
High
Retain Physical Machine/Virtual Machine Image App Binary
Operating System Files
Memory
•
Uned OS and applications
•
Legacy applications that do not have
Data
Disk Volumes
a business justification for migrating to the cloud
NIC
Retain
Disk Drives
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
Rearchitect (Replace)
Retire Physical Machine/Virtual Machine Image App Binary
Operating System Files
Memory
NIC
Retain
•
Duplicate resources due to M&A
•
Resources part of an existing
Data
Disk Volumes
decommissioning program scope •
Clustered hosts for DR purposes
•
Alternative HA hosts
Disk Drives
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
Rearchitect (Replace)
Rehost Physical Machine/Virtual Machine Image App Binary
•
Data
App Binary
Operating System Files
Operating System Files
Memory
Disk Volumes
Data
Rehost
software •
New Disk Volumes
Retain
Amazon EC2
Disk Drives
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Applications without an active roap
• NIC
Servers running packaged
Ad hoc, dev, and test environments
Refactor
Rearchitect (Replace)
Rehost Pros
Cons
Speed of migration Reduced risk of migration AWS + partner ecosystem-offered tools to natively this migration strategy Migration could be application, hypervisor, and physical hardware agnostic
Rehost is not OS agnostic; you will retain the same OS and settings in the target environment You may not use AWS services that give you operational scale like Amazon RDS, Amazon Redshift, and so on
Could be automated/tool assisted
Inherit potentially same application performance characteristics
s migration of system with configuration
You don’t get to retire much technical debt
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
Rearchitect (Replace)
Best practices for Rehost • Utilize AWS and/or partner tools for increased velocity of your migration initiative • Set up Migration Factory with AWS/partner help • Evaluate and understand your infrastructure environment • Challenge yourself to improved architecture • Exercise migrations before doing a cutover
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
AWS Server Migration Service (AWS SMS)
Rearchitect (Replace)
Replatform •
Physical Machine/Virtual Machine Image App Binary
Data
Replatform
App Binary
Data
•
Operating System Files Fresh New OS
Memory
Disk Volumes
NIC
Disk Drives
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
New Disk Volumes
EC2
Rehost
Replatform
•
•
Changing the OS or DB engine Upgrading to the latest release of an application Upgrading the OS from Windows 2003 to Windows 2008/2012 Upgrading from Oracle 8 to Oracle 11
Refactor
Rearchitect (Replace)
Replatform Pros
Cons
Option to use cloud services that are close to existing infrastructure without requiring code change, for example, RDS, Amazon Aurora, Amazon EFS, Amazon WorkSpaces
Some Replatform projects may be timeconsuming and costlier
No dependency on OS, hypervisor or underlying physical hardware platform
Requires additional planning and coordination
Might require both the existing and new environment to run in parallel
Migrating to newer platform/OS/DB Opportunity to utilize modern OS/DB features/functionality Automated tools assisted option avaialble in some cases
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
Rearchitect (Replace)
Best practice for Replatform • • • • • • •
Evaluate code dependencies on OS Identify any modifications required in the code to port it on a new OS Evaluate if porting would require any functionality trade-offs Communicate trade-offs with base and partners Wherever possible, break up each functional component and test them individually Consider hybrid environment and plan your migration appropriately If environments are running in parallel, consider DNS switch method post successful testing Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
AWS Database Migration Service (AWS DMS)
Rearchitect (Replace)
Refactor Physical Machine/Virtual Machine Image App Binary
Data
Refactor
App Binary
Data
Operating System Files
New Operating System
Memory
Disk Volumes
New Disk Volumes
NIC
Disk Drives
EC2
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
•
Changing middleware
•
Recoding application components
•
Changing application code to utilize cloud native feature for performance, scaling, agility
Refactor
Rearchitect (Replace)
Refactor Pros
Cons
Application with a new lifeline, utilizes cloud native features Increased efficiency, agility at improved cost Refactor strategy is application code, OS, hypervisor and hardware agnostic
Could be complicated Requires a very good understanding of all aspects of the application, compliance, regulatory, security, code, design, and so on Could be expensive
Flexibility in porting and globalization
Migration timelines could be extended
Adaptive to modern consumer needs
Additional resource requirement by the business
Better customer experience
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
Rearchitect (Replace)
Best practice for Refactor • • • • • •
Scope your Refactoring initiative to a desired business outcome, don’t make it a reengineering project Make sure your code is working as expected and baseline current functionality and features Make sure you have documented test procedures (and tools) for regular testing after each component of your code is refactored Consider this as an opportunity to introduce good CI/CD practice and tools, this would allow quick development, testing, rollout and rollback Break each refactoring down into small project, ensuring the delivered code matches the desired functionality Use automated refactoring tool if there is one available for your use case; for example, if your application is C++, you might be able to use Lint, Visual Assist, Visual Studio Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
PaaSLane
Refactor
Rearchitect (Replace)
Rearchitect (Replace) Physical Machine/Virtual Machine Image App Binary
Data
Rearchitect
Data
$aaS on
Operating System Files
Hosted Solution Memory
• • •
Disk Volumes
• NIC
Disk Drives
•
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Changing from RISC to x86 Changing application components Rebuilding application architecture Replacing the application with a SaaS offering or COTS product Purchasing a cloudcompatible license
Refactor
Rearchitect (Replace)
Rearchitect (Replace) Pros
Cons
Eliminating dependency on custom hardware or proprietary technology platforms
Careful evaluation of partners/vendors required
With Replace strategy, no infrastructure to maintain
Some Rearchitect use cases grow in time and effort, covering Replatform, and Refactor
Pay for what you use with SLAs
Data migration still required, even if Replace is the strategy
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
Rearchitect (Replace)
Best practice for Rearchitect (Replace) •
• • •
Evaluate your options, not just from technical functionality perspective, but also consider integrations with partners, financial viability, and security/compliance or regulatory requirements Build and run in parallel and identify options to keep data between the on premise and newer system in sync Test functionalities in batches; benefits vs. vs. payroll and so on Identify base that will be testing each functional component of the new system, migrate in batches as well
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
Rearchitect (Replace)
Comparing cloud migration strategies All dimensions of time, cost and agility are relative to migration strategies presented on this slide Retain
Retire
Rehost
Replatform
Refactor
Time
Cost
Agility
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Balanced
Rewarding
Rearchitect (Replace)
Case Study
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Who is Scholastic?
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Who is Scholastic? • Our mission: To encourage the intellectual and personal growth of all children, beginning with literacy • Started in 1920 with a single magazine • The largest publisher and distributor of children’s books in the world • 165 countries, 45 languages • A leading provider of educational materials in K–8
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Strategic things that matter • • • • • • •
Costs Uncertainty Flexibility Risk Scale Organization Strategy and reputation
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Key cost factors • • • • • •
Current costs Like for like costs Ideal architecture costs Pain point costs Transition costs Opportunity costs
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Analysis approaches • Retain or Rehost: macro analysis • Replatform, Rearchitect: architectural analysis • Rehost, Refactor, Rearchitect: • Cost avoidance, feature/scale requirements
• Retire, Rearchitect, Refactor: • Business alignment • Lifespan
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Scholastic’s migration mantras • Everything must go! • One step at a time • Find one win • Improve one thing
• Do or do not, there is no try • When in doubt, move it • In the cloud, incremental improvement == $ © 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Scholastic: Retain (Revisit) • Our example: e-commerce platform • Why: • • • • •
Recent infrastructure investment Older technology with few cloud examples Proprietary third party software, no obvious Limited depth of expertise in-house Limited lifespan
• Cost and risk of moving >> leaving in place • Limited value in moving
• Outcome: left in place for 2+ years until retired © 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Scholastic: Rehost <-> Replatform • Our example: marketing website infrastructure • Why: • • • • •
Status quo was not viable Technologies very well ed by AWS Strong in-house team Low risk migration path Lots of independent pieces, easily testable.
• Cost and risk of moving < leaving in place.
• Outcome: migration + upgrades over 3-month span © 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Scholastic: Rearchitect • Our example: digital platform • Why: • • • • •
Status quo was not viable Desire for investment Strong future product growth Strong development team Good architectural and service fit
• Outcome: Radical cost and performance improvements
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Scholastic: Refactor (+ Replatform) • Our example: identity services • Why: • • • • • • •
General architecture was stable Relatively small changes Good match for AWS Obvious and self-contained pain points Strong development team Status-quo at breaking point New solution available
• Outcome: launched May, 10x performance benefits, 5– 10x reliability/recovery improvement © 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Scholastic: Retire • Our example: legacy web products • Why: • • • • • •
EOL technology No clear migration path (cloud or other) No clear refactoring path No clear replatform option No funding source or clear ROI horizon Overlap with other enterprise options
• Outcome: Almost all legacy technologies retired. Some product lines retired. © 2016, Amazon Web Services, Inc. or its s. All rights reserved.
AWS-Provided Migration Tools Simplify the Journey Planning
Server and DB Migration
Data Transfer
Post Migration Validation
Access partner tools
AWS Application Discovery Service
AWS Server Migration Service
S3 Transfer Acceleration
CloudWatch
AWS Marketplace
AWS Architecture Center
AWS Database Migration Service
AWS Storage Gateway
VMWare Cloud on AWS
AWS Snowball AWS Direct Connect Amazon Kinesis Firehose
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
What’s Next? Application portfolio migration Application discovery, planning, and migration tracking in one place
Better understand your application portfolio
Migrate and Validate
Plan
Discover
Streamline app migration planning and tracking
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
More easily view migration progress
Reduce time spent determining current status
Operate and Optimize
Thank you!
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
to complete your evaluations!
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Related Sessions ENT218 - Simplify Cloud Migration with AWS Server Migration Service ENT312 - Develop Your Migration Toolkit ARC316 - Hybrid IT: A Stepping Stone to All-In ARC314 - Enabling Enterprise Migrations: Creating an AWS Landing Zone For more information, please visit https://aws.amazon.com/migration/partner-solutions/
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Agenda In this session, we will cover: • The 6 Rs of migration • Assessment-based approach • Considerations when selecting the various Rs • Discuss each R of migration strategy • How Scholastic leveraged the 6 Rs
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
6 Rs migration strategy • Customers will keep host/application in their source environment • Minimal analysis/validation of scope and application affinity • Dependency on integrating service management
1
Retain (Revisit) • Application and host decommission on source • No migration to target • Application owner approvals needed
2
Retire 3
Rehost
4
• Up-version of the OS and/or database onto the target cloud • Some level of application changes • Application reinstallation on the target • Database to Amazon RDS
Replatform 5
• OS and/or database porting • Middleware and application change to cloud service offering • Data conversion; Database transition to MySQL, Amazon Aurora, or other
Refactor • Like for like application migration to target cloud • Minimal effort to make the application work on the target cloud infrastructure (minimal application layout change) • Storage migration will be needed (without conversion)
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
6
• Application architecture changes may also require Up-version or Porting • Use SaaS-based offerings, application architecture changes may require porting • Middleware, data modernization; application consolidation/stacking
Rearchitect (Replace)
Assessment-based approach • Financial assessment • Security assessment • Compliance and regulatory assessment • Business assessment • Technical assessment • Contractual assessment
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Application considerations • • • • •
What is the application roap? What are the costs associated with this application? What improvement options are available to enhance service? Are there any risks of not making changes to this application? Where does this application align with the technology goals of the organization?
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Mapping drivers to migration strategy High
Rearchitect (Replace)
Business Agility/Value
Refactor Replatform Rehost
Retain (Revisit) Retire
Low
Migration Effort
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
High
Retain Physical Machine/Virtual Machine Image App Binary
Operating System Files
Memory
•
Uned OS and applications
•
Legacy applications that do not have
Data
Disk Volumes
a business justification for migrating to the cloud
NIC
Retain
Disk Drives
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
Rearchitect (Replace)
Retire Physical Machine/Virtual Machine Image App Binary
Operating System Files
Memory
NIC
Retain
•
Duplicate resources due to M&A
•
Resources part of an existing
Data
Disk Volumes
decommissioning program scope •
Clustered hosts for DR purposes
•
Alternative HA hosts
Disk Drives
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
Rearchitect (Replace)
Rehost Physical Machine/Virtual Machine Image App Binary
•
Data
App Binary
Operating System Files
Operating System Files
Memory
Disk Volumes
Data
Rehost
software •
New Disk Volumes
Retain
Amazon EC2
Disk Drives
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Applications without an active roap
• NIC
Servers running packaged
Ad hoc, dev, and test environments
Refactor
Rearchitect (Replace)
Rehost Pros
Cons
Speed of migration Reduced risk of migration AWS + partner ecosystem-offered tools to natively this migration strategy Migration could be application, hypervisor, and physical hardware agnostic
Rehost is not OS agnostic; you will retain the same OS and settings in the target environment You may not use AWS services that give you operational scale like Amazon RDS, Amazon Redshift, and so on
Could be automated/tool assisted
Inherit potentially same application performance characteristics
s migration of system with configuration
You don’t get to retire much technical debt
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
Rearchitect (Replace)
Best practices for Rehost • Utilize AWS and/or partner tools for increased velocity of your migration initiative • Set up Migration Factory with AWS/partner help • Evaluate and understand your infrastructure environment • Challenge yourself to improved architecture • Exercise migrations before doing a cutover
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
AWS Server Migration Service (AWS SMS)
Rearchitect (Replace)
Replatform •
Physical Machine/Virtual Machine Image App Binary
Data
Replatform
App Binary
Data
•
Operating System Files Fresh New OS
Memory
Disk Volumes
NIC
Disk Drives
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
New Disk Volumes
EC2
Rehost
Replatform
•
•
Changing the OS or DB engine Upgrading to the latest release of an application Upgrading the OS from Windows 2003 to Windows 2008/2012 Upgrading from Oracle 8 to Oracle 11
Refactor
Rearchitect (Replace)
Replatform Pros
Cons
Option to use cloud services that are close to existing infrastructure without requiring code change, for example, RDS, Amazon Aurora, Amazon EFS, Amazon WorkSpaces
Some Replatform projects may be timeconsuming and costlier
No dependency on OS, hypervisor or underlying physical hardware platform
Requires additional planning and coordination
Might require both the existing and new environment to run in parallel
Migrating to newer platform/OS/DB Opportunity to utilize modern OS/DB features/functionality Automated tools assisted option avaialble in some cases
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
Rearchitect (Replace)
Best practice for Replatform • • • • • • •
Evaluate code dependencies on OS Identify any modifications required in the code to port it on a new OS Evaluate if porting would require any functionality trade-offs Communicate trade-offs with base and partners Wherever possible, break up each functional component and test them individually Consider hybrid environment and plan your migration appropriately If environments are running in parallel, consider DNS switch method post successful testing Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
AWS Database Migration Service (AWS DMS)
Rearchitect (Replace)
Refactor Physical Machine/Virtual Machine Image App Binary
Data
Refactor
App Binary
Data
Operating System Files
New Operating System
Memory
Disk Volumes
New Disk Volumes
NIC
Disk Drives
EC2
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
•
Changing middleware
•
Recoding application components
•
Changing application code to utilize cloud native feature for performance, scaling, agility
Refactor
Rearchitect (Replace)
Refactor Pros
Cons
Application with a new lifeline, utilizes cloud native features Increased efficiency, agility at improved cost Refactor strategy is application code, OS, hypervisor and hardware agnostic
Could be complicated Requires a very good understanding of all aspects of the application, compliance, regulatory, security, code, design, and so on Could be expensive
Flexibility in porting and globalization
Migration timelines could be extended
Adaptive to modern consumer needs
Additional resource requirement by the business
Better customer experience
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
Rearchitect (Replace)
Best practice for Refactor • • • • • •
Scope your Refactoring initiative to a desired business outcome, don’t make it a reengineering project Make sure your code is working as expected and baseline current functionality and features Make sure you have documented test procedures (and tools) for regular testing after each component of your code is refactored Consider this as an opportunity to introduce good CI/CD practice and tools, this would allow quick development, testing, rollout and rollback Break each refactoring down into small project, ensuring the delivered code matches the desired functionality Use automated refactoring tool if there is one available for your use case; for example, if your application is C++, you might be able to use Lint, Visual Assist, Visual Studio Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
PaaSLane
Refactor
Rearchitect (Replace)
Rearchitect (Replace) Physical Machine/Virtual Machine Image App Binary
Data
Rearchitect
Data
$aaS on
Operating System Files
Hosted Solution Memory
• • •
Disk Volumes
• NIC
Disk Drives
•
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Changing from RISC to x86 Changing application components Rebuilding application architecture Replacing the application with a SaaS offering or COTS product Purchasing a cloudcompatible license
Refactor
Rearchitect (Replace)
Rearchitect (Replace) Pros
Cons
Eliminating dependency on custom hardware or proprietary technology platforms
Careful evaluation of partners/vendors required
With Replace strategy, no infrastructure to maintain
Some Rearchitect use cases grow in time and effort, covering Replatform, and Refactor
Pay for what you use with SLAs
Data migration still required, even if Replace is the strategy
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
Rearchitect (Replace)
Best practice for Rearchitect (Replace) •
• • •
Evaluate your options, not just from technical functionality perspective, but also consider integrations with partners, financial viability, and security/compliance or regulatory requirements Build and run in parallel and identify options to keep data between the on premise and newer system in sync Test functionalities in batches; benefits vs. vs. payroll and so on Identify base that will be testing each functional component of the new system, migrate in batches as well
Retain
Retire
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Rehost
Replatform
Refactor
Rearchitect (Replace)
Comparing cloud migration strategies All dimensions of time, cost and agility are relative to migration strategies presented on this slide Retain
Retire
Rehost
Replatform
Refactor
Time
Cost
Agility
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Balanced
Rewarding
Rearchitect (Replace)
Case Study
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Who is Scholastic?
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Who is Scholastic? • Our mission: To encourage the intellectual and personal growth of all children, beginning with literacy • Started in 1920 with a single magazine • The largest publisher and distributor of children’s books in the world • 165 countries, 45 languages • A leading provider of educational materials in K–8
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Strategic things that matter • • • • • • •
Costs Uncertainty Flexibility Risk Scale Organization Strategy and reputation
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Key cost factors • • • • • •
Current costs Like for like costs Ideal architecture costs Pain point costs Transition costs Opportunity costs
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Analysis approaches • Retain or Rehost: macro analysis • Replatform, Rearchitect: architectural analysis • Rehost, Refactor, Rearchitect: • Cost avoidance, feature/scale requirements
• Retire, Rearchitect, Refactor: • Business alignment • Lifespan
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Scholastic’s migration mantras • Everything must go! • One step at a time • Find one win • Improve one thing
• Do or do not, there is no try • When in doubt, move it • In the cloud, incremental improvement == $ © 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Scholastic: Retain (Revisit) • Our example: e-commerce platform • Why: • • • • •
Recent infrastructure investment Older technology with few cloud examples Proprietary third party software, no obvious Limited depth of expertise in-house Limited lifespan
• Cost and risk of moving >> leaving in place • Limited value in moving
• Outcome: left in place for 2+ years until retired © 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Scholastic: Rehost <-> Replatform • Our example: marketing website infrastructure • Why: • • • • •
Status quo was not viable Technologies very well ed by AWS Strong in-house team Low risk migration path Lots of independent pieces, easily testable.
• Cost and risk of moving < leaving in place.
• Outcome: migration + upgrades over 3-month span © 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Scholastic: Rearchitect • Our example: digital platform • Why: • • • • •
Status quo was not viable Desire for investment Strong future product growth Strong development team Good architectural and service fit
• Outcome: Radical cost and performance improvements
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Scholastic: Refactor (+ Replatform) • Our example: identity services • Why: • • • • • • •
General architecture was stable Relatively small changes Good match for AWS Obvious and self-contained pain points Strong development team Status-quo at breaking point New solution available
• Outcome: launched May, 10x performance benefits, 5– 10x reliability/recovery improvement © 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Scholastic: Retire • Our example: legacy web products • Why: • • • • • •
EOL technology No clear migration path (cloud or other) No clear refactoring path No clear replatform option No funding source or clear ROI horizon Overlap with other enterprise options
• Outcome: Almost all legacy technologies retired. Some product lines retired. © 2016, Amazon Web Services, Inc. or its s. All rights reserved.
AWS-Provided Migration Tools Simplify the Journey Planning
Server and DB Migration
Data Transfer
Post Migration Validation
Access partner tools
AWS Application Discovery Service
AWS Server Migration Service
S3 Transfer Acceleration
CloudWatch
AWS Marketplace
AWS Architecture Center
AWS Database Migration Service
AWS Storage Gateway
VMWare Cloud on AWS
AWS Snowball AWS Direct Connect Amazon Kinesis Firehose
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
What’s Next? Application portfolio migration Application discovery, planning, and migration tracking in one place
Better understand your application portfolio
Migrate and Validate
Plan
Discover
Streamline app migration planning and tracking
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
More easily view migration progress
Reduce time spent determining current status
Operate and Optimize
Thank you!
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
to complete your evaluations!
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Related Sessions ENT218 - Simplify Cloud Migration with AWS Server Migration Service ENT312 - Develop Your Migration Toolkit ARC316 - Hybrid IT: A Stepping Stone to All-In ARC314 - Enabling Enterprise Migrations: Creating an AWS Landing Zone For more information, please visit https://aws.amazon.com/migration/partner-solutions/
© 2016, Amazon Web Services, Inc. or its s. All rights reserved.
Related Documents 3h463d
6rs Of Migration Aws Reinvent 5u2a6g
October 2022 0
Reinvent Yourself - James Altucher 4g6j3t
July 2020 0
Igcse Migration And Gcse Migration 6c2j4n
January 2022 0
Audit Report Of Data Migration 4b4r3x
November 2019 21
Aws Bookstore. Aws D1.8_d1 5h6o6i
December 2019 75
Advantages And Disadvantages Of Migration 4w61g
November 2019 171More Documents from "wasim haque" 4kv21
6rs Of Migration Aws Reinvent 5u2a6g
October 2022 0
Wifi Technology.pdf 6a4j30
December 2019 48
Communication And Networking Concepts Full Forms.pdf 301r4y
October 2021 0
Film Financing g3uq
December 2019 81
1.docxd 2j11m
December 2019 12