Migrating large fleets of legacy applications to AWS cloud infrastructure requires careful planning, since each phase needs to balance risk tolerance against the speed of migration.
Through participation in many large-scale migration engagements with customers, AWS Professional Services has developed a set of successful best practices, tools, and techniques that help migration factories optimize speed of delivery and success rate. In this session, we cover the complete lifecycle of an application portfolio migration with special emphasis on how to organize and conduct the assessment and how to identify elements that can benefit from cloud architecture.
1. November 14, 2014 | Las Vegas, NV
Paul Nau, Senior Consultant, AWS Professional Services
Miha Kralj, Principal Consultant, AWS Professional Services
Aman Bhutani and Magesh Chandramouli, Expedia Worldwide Engineering
2.
3. •Conduct application discovery workshop
•Interview application owners
•Implement tool-based discovery
•Profiling application inventory
•Identifying complexity, criticality and preferences
•Clustering and prioritizing
•Driven by prioritization, skills and best practices
•Use best patterns
•Capture inter- dependencies
•From “lift and shift” to “drop and shop”
•Expect complete IT transformation
•Include IT process changes and organizational change management
•Focus on new Operations model
Application portfolio assessment
Collecting application portfolio inventory
Defining segmentation and prioritization criteria
Determining application migration options
Creating application migration roadmap
5. •Business criticality (frequency of use, size of user base, supported business process)
•Deriving consequence factor of failure
•Technology complexity (dependencies, fragility, understandability of the app)
•Deriving probability of failure
•Sizing (how many systems, data volumes, storage size, other volumetric requirements)
•Deriving effort of migration
•HA/DR/BCP (continuity plans, availability requirements, backup/restore requirements)
•Deriving pre-and post-migration effort (cost of support and keeping the app current)
Segmentation and prioritization criteria
7. Discover/assess/prioritize
applications
Migration Tools
Transition
Production
Retain / not moving
Redesign application/
Infrastructure architecture
App code
development
Purchase COTS/
SaaS & licensing
Test
Modify underlying
infrastructure
Full ALM /
SDLC
Manual config
Manual deploy
Manual install
Retire / decommission
Determine
migration path
Automated
Manual install
& setup
Integration
Actual application migration patterns
8. Measured elastic IT resourcethat can be rapidly provisionedon-demand, such as: Object storage service
Service
A technology collectionthat can be transparently obtained from collection of available stencils, such as a LAMP stack
Stack
An aggregated IT functionalityperformed by collection of various IT stacks, such as:Managed Desktop
Workload
An abilityof IT to provide value to the business through a collection IT workloads, such as: Line of Business Platform
IT Capability
An IT componentthat includes pre-defined and configured cloud services, such as Spot instances in auto-scaling group
Template
9. Foundational Services
Platform Services
Security
Firewall
Identity & Access
Auditing
Encryption
Storage
Object Store
File Store
Archiving
Backup/Recovery
Storage Integration
Compute
General Purpose
Compute optimized
Memory Optimized
GPU Optimized
Storage Optimized
Server OS
Linux
BSD
Windows
Other
Data Integration
ETL/ELT
Replication
Queueing
Data Load
MDM
App Services
Mobile
App Store
Push
Analytics
Identity
Composites
Search
Workflow
Messaging
Streaming
Transcoding
Orchestration
Protocols
http
REST
SMTP
IM/SMS
SOAP/WS-*
RDP/VNC
SSH
Clients
Browser
Email
Legacy App
Mobile App
TXT
Store app
Term
Data Analytics
Data streaming
Data Processing
Data Mining
Machine Learning
Event Processing
Networking
Cloud Isolation
Connectivity
Elasticity
Name Resolution
Content Delivery
App Server
Java
PHP
Python
Ruby
.NET
Node.js
SAP
Database
Relational
NoSQL
In-memory DB
Data Warehouse
HANA
12. Cloud Adoption Strategic Initiative
Launch and mobilize
Cloud Adoption –Service Analysis & Design
Maturity and Gap Analysis
Cloud Technology Foundation Design
IT Organization Redesign
IT Process Redesign
Application Portfolio Assessment
Cloud Adoption –Service Transition
Integrated IT Operating model
Provisioning, Migrations, Handover
Cloud Adoption –Service Operations
Monitoring, ITSM Management
SLA Management, Billing, Reporting
Cloud Adoption –Portfolio Governance
Weeks 1-4
Weeks 5-8
Weeks 9-12
Weeks 13-16
Weeks 17-20
Weeks 21-24
Weeks 25-28
Weeks 29+
Define Cloud Strategy & Team
13. Architecture team
Lead Architect
Migration team
Migration Lead
Operations team
CloudOperations Lead
PM Office
Head Scrum Master
Security Lead
Networking Lead
Foundation Lead
Cloud Ops -Network
Storage & DB Lead
Linux compute Lead
Windows compute Lead
Automation Lead
DevOpsLead
Project Manager
Web migration Lead
Linux app stack Lead
Win app stack Lead
Oracle DB Lead
Cloud Ops -Automation
Cloud Ops –Front-end
Cloud Tooling Lead
Cloud Ops –Middleware
Cloud Ops –Database
CIO Office
Cloud Program Lead
14. November 14, 2014 | Las Vegas, NV
Aman Bhutani and Magesh Chandramouli,
Expedia Worldwide Engineering
15. A WALK IN THE CLOUD
Chief
Developer
Chief
Overhead
16. 1. EMBARKING ON THE JOURNEY
•Build expertise
•Application assessment
•Non-PCI
•Content based
•Low risk, decent impact
•Regular results
•Self-fund initial experiments
•Establish trust
17. 2. GET ALL YOUR STUFF READY –MAKE IT EASY!
•Prime
•Hubble
•Deployer
•Hopscotch
•Primer
22. 2.5 PRIMER – ASSEMBLY LINE FOR APPLICATIONS
Ticker
23. 3. START THE JOURNEY; DON’T HESITATE TO ITERATE
•Interopkey dependencies
•Send traffic to local region
•Start with 1%
•Transparent to customer
•Willing to destroy / upgrade