The document discusses migration to AWS and modernization. It notes that migration, modernization, and innovation go hand in hand. Migrating existing technology debt to the cloud provides value more slowly than developing cloud-native applications. The modernization process involves determining migration paths, assessing applications, and iteratively replatforming and redesigning applications and infrastructure on AWS. Common patterns for successful migration include discovery of existing assets, establishing business cases, early experimentation, defining target operating models, and change governance. Common blockers include building business cases, partner selection, security concerns, capability gaps, and operational uncertainties.
9. B2C company Cloud Transformation journey
DC
Migration/Refresh
Readiness
and
Planning
GreenPlum RedShift
DC
Migration/Refresh
Assessment
and
Business Case
DC1
refresh/exit
H1 2017 H2 2017 H2 2017 2018 2019 2020
Breaking-out GISV monolith into
discrete home-grown services (i2)
Instiutionalising
DevOps
Time critical path activities
Non time critical path activities
Input
Experimentation…
Personalization
analytics
hours->seconds
Predominantly server-based
product architecture in owned DCs
Predominantly serverLESS
product cloud architecture
~3,000
servers
60%+ business functionality
provided by monolithic Global ISV
(GISV) packaged application
Business functionality
provided by GISV application
reduced to 10%
=<1,000
Servers(instances)
Customer eXPerience
platform (re)engineering
PersonaliZatioN
service (re)engineering
DC2
refresh/exit
Application platform
service (re)engineering
State Regulator
infrastructure location
constraints
and on-going negotiationsProgressive
server->service
migrations
(on-prem and cloud)
2018 company roadmap
People/Capability Development
DC
Migration/Refresh
Program
of
Work
Digital Innovation
envisioning