Modernization involves implementing business processes and technology that provide your business applications with high availability, agility, and elasticity. Nowhere is this more important than in breaking apart the monolith. Modernizing an application as part of a migration can be extremely successful if you follow the AWS migration methodology of “discover, plan, migrate, and optimize” as you move that application to the cloud. In this session, we share what we learned from over 400 successful migrations. We also show you how to virtually break a monolith to a modernized architecture as part of the planning phase and accelerate your migration using container technologies and application discovery tools.

2. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Breaking Up the Monolith While
Migrating to AWS
G P S T E C 3 2 0
Carmen Puccio
Principal Solutions Architect
AWS Partner Program
Mandus Momberg
Principal Solutions Architect
AWS Partner Program
Peter Hack
Sr. Technical Evangelist
Dynatrace

3. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
The monolith
“…a single-tiered software application in which the user
interface and data access code are combined into a single
program from a single platform. A monolithic application is
self-contained, and independent from other computing
applications.”
- Wikipedia

4. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Monolith = ”traditional applications”
• Pros:
• At first…
• Simple
• No over-engineering
• In-process latencies
• Single code base
• Resource efficient at small
scale
• Cons:
• Modularity is hard to
enforce as app grows
• Can only scale up!
• All or nothing deployment
• Long release cycles
• Slow to react to customer
demand

5. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Monolith development lifecycle
Build Test Release
Developers
Monolith
Delivery Process

6. How or why should I migrate my
monolith?

7. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Common migration strategies
There is no one size fits all approach to migrating your applications

8. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Methodical migration process
Evaluate Plan Design Migrate Optimize
• Discovery
• Migration
patterns
• Well Architected
• Tool selection
• Test planning
• Cutover planning
• Migration
workloads
• Migration tools
• Validation &
cutover
• Operation
• Optimization
• Migration
Readiness
Assessment
• On-boarding
• Planning and SOW
• Portfolio
discovery
• Requirements
collection
• Landing Zone
• People - skills and
organization
• Business case, TCO
Visualize the cloud adoption effort from planning to operating on AWS

9. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Portfolio discovery
Goals:
• Determine resource allocation in the AWS environment
• Develop a prioritized backlog of applications to feed migration
• Assess project migration costs and run costs
Evaluate
Discover
& Plan
Design Migrate Optimize

10. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Questions & challenges on the migration journey
• Where to start?
• What to break out?
• Dependencies?
• Works as expected?
• Users happy?
• Does it scale?
• Does it perform?
• How to automate?
• Works as expected?
• Users happy?
• How to optimize?
Does it perform?
• How to automate?
?
? ?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
? ?
?
?
?
? ? ?
?
?
?
?
From
On-Premises Monolith
Via
Containerized Services
To
Functions & Cloud Services

11. Should I consider containers as part
of my migration strategy?

12. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Accelerate
Development
Easier
Adoption
Faster
Iteration
Unified
Experience
Container Platforms
Container Benefits

13. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Customers using containers on AWS

14. But what does this buy me?

15. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Cost savings opportunities
Containers can help drive costs down
• Better resource utilization
• Simplify maintenance
• Faster software delivery
• Opportunities for EC2 Spot Instances

16. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Deployment benefits
A typical deployment workflow
AWS
CodePipeline
Developers Git repository Amazon
ECR
Amazon ECS Amazon EKS
AWS Fargate

17. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Modern development lifecycle
Build Test Release
Build Test Release
Build Test Release
Developers Services Delivery Pipelines

18. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Rolling deployments
Max: 200%
minHealthy: 100%
Update service
Amazon
ECS
Max: 100%
minHealthy: 75%
Service A
Task definition: 2
Desired count: 4

19. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Canary blue-green deployments
More at:
Task
100%
0%

20. Where do I start?

21. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Discovery – Portfolio Data Gathering
• Storage
• Type
• Capacity
• Utilization
• . . .
• Server
• Physical/virtual
• OS version
• CPU, RAM, Disk
• type, utilization
• . . .
• Network
• Device type
• Firewall rule
• Network
connection
• . . .
• Application
• Owners,
criticality
• Characteristics
• Stack
• Infrastructure
• . . .

22. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Analysis … What Should We Look For?
• Completeness and usability
• If additional discovery is needed, determine the actions needed to complete discovery.
• Apps, Servers,
Connections
• No. of apps and servers
• Application and server
dependencies
• Performance
metrics
• Allocate and right-
size target resources
• Service naming,
tagging
• Identify patterns
• Group servers and
applications

23. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Asset
Inventories
CMBD
Tribal
Knowledge
SLA/OLA
App
Configuration
Data
Performance
Information
Architecture
Outcomes
Applications
Infrastructure
Performance
Portfolio Discovery & Analysis Outcomes
Resource Model
Application backlog
Cost Model
AWS Application
Discovery Service
Disconnected and
Incomplete Data
Gathering Data and
Organizing
“Discovery & Planning”

24. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Dynatrace Smartscape
We tell you WHAT to migrate and
WHERE to break the monolith!
Dynatrace AI
Automatic End User, Service and
Infrastructure Root Cause Analysis
Dynatrace Automation API
Automate Rollout in your
Containers & Functions. Automate
Shift-Left and Self-Healing
Dynatrace
• Where to start?
• What to break out?
• Dependencies?
• Works as expected?
• Users happy?
• Does it scale?
• Does it perform?
• Works as expected?
• Users happy?
• How to optimize?
Does it perform?
• How to automate?

25. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Dynatrace helps decide what to migrate
Dynatrace Smartscape
• Auto-dependency
mapping of internal
& external services
• Auto-load detection
and baselining
• Auto-resource
consumption
detection

26. “The value we get from Dynatrace is on a day-to-day basis, proactively preventing
outages from occurring in the first place. Dynatrace's AI capabilities mean we don't
have to waste crucial time trawling through logs to identify the root cause when
tests fail; it just gives us instant answers.”
Chris Burrell, Head of Tech, Landbay
https://www.dynatrace.com/company/customers/landbay/

27. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Getting to know the monolith architecture
?
?
?
?
?
?
?
?
?
?
?
Service
Endpoints
Service Flow
Depending
Services

28. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Step #1 Dependency Information
ExampleCorp
ExampleCorpWebserver:18079
ExampleCorpWebserver:18079
ExampleCorpBackendWebServer:8091

29. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Step #2 Detecting Service Endpoints
Endpoints CPULoad
ExampleCorp ExampleCorp
ExampleCorp
ExampleCorp ExampleCorp
ExampleCorp

30. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Step #3 Understanding Service Flow per Endpoint
#1 Filter on specific endpoint
#2 See Execution Flow to Depending Services
#3 Dependencies
& Call Patterns
#4 Call Pattern Details
exampleCorp
ExampleCorpBackendWebser...exampleCorp
exampleCorp
exampleCorp

31. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Step #3 Understanding Service Flow per Endpoint
#1 Filter on specific endpoint
#2 See Execution Flow to Depending Services
#3 Dependencies
& Call Patterns
#4 Call Pattern Details
exampleCorp
exampleCorp
exampleCorp Customer Fron...
exampleCorp Customer Frontend
ExampleCorpWebserver:18079
exampleCorp-Buisiness
PHP on exampleCorpWebser...

32. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
What we have learned so far!
/review
/finish
/config
/payment
Backend
Service X
DB A
Q 1
Endpoints +
Throughput
Dependencies &
Call Patterns
Flow & CPU
Consumption

33. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Next: Where to break the monolith?
/review
/finish
/config
/payment
Backend
Service X
DB A
Q 1
?
?
?
?
?
?
?
?
?
?
Entry Points? Entry Points?

34. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Step #4: Finding Entry Points with CPU Sampling
#1 Filter on specific endpoint
#2 Search for specific code
#3 Found Entry Point to Package
exampleCorp
.examplecorp.
.examplecorp.
.examplecorp.

35. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Step #5 Define Custom Service Entry Points
#1 Service Name
#2 Methodcom.dynatrace.examplecorpfrontend.beans.BookingBean
com.dynatrace.examplecorpfrontend.beans.BookingBean

36. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
We “virtually” broke the monolith!
/review
/finish
/config
/payment
Backend
Service X
DB A
Q 1
User
Catalog
Check
Avail.
Credit-
Card
Billing
Order
Journey
Booking
Configuration
Payment

37. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Refactoring – break the monolith
Tightly coupled! Shall we really distribute/extract?
ExampleCorpBackendWebser...
com.Dynatrace.exampleCorp...

38. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Dynatrace Baselining Validates Before vs. After!
Before After

39. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Dynatrace Container Monitoring
Automatic Injection & Meta
Data Extraction!
Automatic Service Monitoring within the
Containers

40. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.

41. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Related breakouts
Monday, Nov 26
SRV322-R - From Monolith to Modern Apps: Best Practices
4:00pm – 5:00pm | Mirage, Montego D
Tuesday, Nov 27
CON203-R1 - From the Data Center to the Cloud with
Containers
10:45 AM – 11:45 AM | Venetian, Level 2, Venetian Theatre
Wednesday, Nov 28
CON348-R1 - Containerizing Legacy .NET Workloads
1:00 PM – 2:00 PM | Bellagio, Level 1, Degas 2

42. Thank you!
© 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Carmen Puccio
@CarmenAPuccio
Mandus Momberg
@MandusMomberg
Peter Hack
@hackatdt

43. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.