9. Migration to Modernization Strategy
Value
from the
Cloud
Re-host
Re-platform
Refactor
Rearchitect
Rewrite
Continuous
Modernization
BREADTH OF CHANGE
BENEFITS
TACTICAL (CONTAINERIZATION)
X No code modernization
X No technical debt removal
X No architectural changes
Improves security
Simplifies DevOps
X No scalability/elasticity
X No accelerated eng velocity
STRATEGIC (MICROSERVICES)
Accelerated engineering velocity
Shorter test & release cycles
Increased scalability & elasticity
Increased innovation
Setting Expectations 1: Migration vs. Modernization
MIGRATION MODERNIZATION
Accelerated rate of change -
aging all applications faster
Today's apps will be legacy
tomorrow
What are you trying to achieve?
10. UI
Business Logic
Database
Setting Expectations 2:
Avoiding Quick Fixes
❌ Backend business logic is still unchanged
❌ Code is still monolithic
❌ No change in scalability, engineering velocity,
or technical debt.
Still a
Monolith
Monolithic Architecture
Modernizing Everything But
the Business Logic
Modernizing the UI first is just putting a shiny
wrapper on a still persistent problem
UI tightly coupled with the business logic
Modernizing the Business Logic
First
Monolith
Break down the monolith business logic and
create new micro frontends for each service
Tackle technical debt head on
Support rapid innovation & engineering velocity
<Decompose the
Business Logic
Monolith
Modernizing the busines logic will bring the
most value and competitive edge