Where to Begin? Application Portfolio Migration - Miha Kralj, Principal Consultant, AWS
Application portfolio assessment is a technique used at the beginning of enterprise application migration process. It helps migration team to gather, analyse and understand their app portfolio before deciding on priorities and sequences of application migration. This session will present the app assessment process, the most common migration strategies and tools, and the placement of application portfolio migration in a complete IT Transformation process.
My INSURER PTE LTD - Insurtech Innovation Award 2024
Where to Begin? Application Portfolio Migration
1. Where to Begin? Application
Portfolio Migration
Miha Kralj
Principal Consultant, Amazon Web Services
2. Agenda
• Application Portfolio Assessment
• The decision flow, segmentation and prioritisation
• Application Migration Factory
• Tools, processes and people required for mass migrations
• Cloud Transformation Framework
• Building the enterprise-wide IT transformation program
3. Application Portfolio Assessment
• Conduct application
discovery workshop
• Interview application
owners
• Implement tool-based
discovery
• Profiling application
inventory
• Identifying complexity,
criticality and
preferences
• Clustering and
prioritizing
• Driven by
prioritisation, 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
organisational change
management
• Focus on new
Operations model
Collecting
Application
Portfolio
Inventory
Defining
Segmentation
and Prioritisation
Criteria
Determining
Application
Migration
Options
Creating
Application
Migration
Roadmap
4. Application Discovery and Collection
• Semi-automated process with
automation rate improving with
experience
• Combination of AWS and partner
tooling with best practices and
custom questionnaires
• Requires light participation/
workshops with business
application owners
• Ranking is specific for each
customer/environment, but is based
on standard AWS approach
• Information collected:
• Name of the app, technical owner, business owner
• Number of systems: direct (exclusive), indirect
(dependent), non-prod (dev-test)
• Infrastructure desc (network, ports/protocols, security,
virtualiser, directory, OS)
• Information desc (database, data classification, data
exchange)
• App desc (app framework, middleware used, web tier
used, dev language)
• Automation tools:
• RISC Network – CloudScape
• ScienceLogic – CloudMapper
• ServiceNow – Service Watch
• Blue Stripe - FactFinder
Collecting
Application
Portfolio
Inventory
5. Segmentation and Prioritisation Criteria
• 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)
Defining
Segmentation
and Prioritisation
Criteria
11. Application Migration Team
Architecture team
Lead Architect
Migration team
Migration Lead
Operations team
Cloud"
Operations 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
DevOps Lead
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
Team
Composition
12. Application Architecture Mapping
An ability of IT to provide value to the
business through a collection IT workloads,
such as: Line of Business Platform
An aggregated IT functionality performed by
collection of various IT stacks, such as: Managed
Desktop
IT Capability
Workload
Measured elastic IT resource that can be rapidly provisioned on-demand,
such as: Object storage service
"
Service
A technology collection that can be transparently obtained
Stackfrom collection of available stencils, such as a LAMP stack
An IT component that includes pre-defined and configured cloud
Stencilservices, such as Spot instances in auto-scaling group
Conceptual
Architecture
13. Foundational ServicesPlatform Services
Networking
Cloud Isolation
Connectivity
Elasticity
Name Resolution
Security
Firewall
Identity & Access
Auditing
Encryption
Storage
Object Store
File Store
Archiving
Backup/Recovery
Storage Integration
Compute
General Purpose
Compute optimised
Memory Optimised
GPU Optimised
Storage Optimised
Server OS
BSD
Linux
Windows
Other
Database
Relational
NoSQL
In-memory DB
Data Warehouse
Data Integration
ETL/ELT
Replication
Queueing
Data Load
MDM
App Services
Composites
Search
Workflow
Messaging
Mobile
App Store
Push
Analytics
Identity
OrchestrationStreaming
Transcoding
Data Analytics
Data streaming
Data Processing
Data Mining
Machine Learning
App Server
Java
PHP
Python
Ruby
.NET
Node.js
Event Processing
Content Delivery
SAP
HANA
Application Modeling Canvass
Logical
Architecture
14. Sample Cloud Adoption Roadmap
Discovery
Workshop
Cloud
Business
Case
Define Network
Environment
Define Security
Requirements
Define
Governance
Structure
Define EA
Policies and
Practices
Operational
Integration
Security
Operations
Playbook
Cloud
Environment
Optimization
Application
Portfolio
Analysis
Cost and
Billing
Analysis
Training and
Certification
Define Cloud
Environments
15. AWS Cloud Adoption Framework
People
Domain
Process
Domain
AWS framework organises and
describes all of the activities and
processes involved in planning,
creating, managing, and supporting a
modern IT service.
Framework offers practical guidance
and comprehensive guidelines for
establishing, developing and running
cloud-based IT capabilities.
It provides a structure where business
and IT can work together towards
common strategy and vision,
supported by modern IT automation
and process optimisation.
Security
Domain
Maturity
Domain
Strategy
and Value
Domain
Platform
Domain
Operating
Domain
16. Cloud Adoption Core Perspectives
Strategy Perspective
Identifying, analyzing and measuring the
effectiveness of IT investments that generate
the most optimal business value.
People Perspective
Selecting and training IT personnel
with appropriate skills, defining
and empowering delivery teams
with accountabilities and service-level
agreements.
Process Perspective
Managing programs and projects
to be on time, on target and within
budget, while keeping risks at
acceptable levels.
Maturity Perspective
Analyzing, defining and anticipating demand
for and acceptance of envisioned IT
capabilities and services. (Charting the right
course)
Platform Perspective
Defining and describing core architectural
principles, standards and patterns that are
required for optimal IT capabilities and
services.
Operating Perspective
Transitioning, operating and optimizing the
hybrid IT environment, enabling efficient and
automated IT Service Management.
Security Perspective
Applying a comprehensive and
rigorous method of describing a
structure and behavior for an
organisation’s security and
compliance processes, systems
and personnel.
17. Conclusions and Recommendations
• Application migration is part of a larger picture
• Requires holistic assessment, planning and integration/transition
• Can be used to demonstrate the approach
• Disposition of each app should be value-driven
• Lift & Shift, Drop & Shop, Refactor & Rewrite
• Plan your own Cloud transformation program
• Every customer is unique, your mileage may vary