Maintaining control of sensitive data is critical in the highly regulated financial investments environment that Vanguard operates in. This need for data control complicated Vanguard's move to the cloud. They needed to expand globally to provide a great user experience while at the same time maintaining their mainframe-based backend data architecture. In this session, Vanguard discusses the creative approach they took to decouple their monolithic backend architecture to empower a microservices architecture while maintaining compliance with regulations. They also cover solutions implemented to successfully meet their requirements for security, latency, and end-state consistency. Speaker: Jon Austin, Enterprise Solutions Architect, AWS

1. From Mainframe to Microservices
Jon Austin
Principal Solutions Architect
Amazon Web Services

2. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Evolving Architectural Patterns in Enterprises
SOA
Coarse-
grained
Microservices
Fine-grained
Monolithic
Single Unit

3. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Why do we need Microservices?
Desire to improve
scalability, availability
& fault tolerance
Improved Deployment Decoupled Systems

4. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Why do we need Microservices?
Re-engineer
the Monolith
Leverage Cloud
Operating Models
Better DevOps
Practices

5. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Characteristics of Microservices
 Reusable modules of code that are built and deployed as independent
entities
 Organized around business capabilities
 Own their domain logic
 Decentralized governance and data management
 Automated and designed for failure

6. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Business Benefits of Microservices
 Reduce Technical Debt
 Eliminate bottlenecks from Monolithic patterns
 Improve velocity

7. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Mainframe to Microservices
Our Goals
Cost Optimize (Reduce MIPS)
Improve Business Agility
Reduce Technical Debt

8. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Migration Pathways
Redesign
Application/
Infrastructure Architecture
App Code
Development
Full ALM /
SDLC
Integration
Purchase COTS/
SaaS & licensing
Manual Install
& Setup
Modify underlying
Infrastructure
Determine
new platform
Retain /
Revisit
Manual Config
Manual Deploy
Manual Install
Use Migration Tools
Transition ProductionValidation
Automate
Discover/Assess/Prioritize
applications
Retire/
Decommission
Determine
migration
path

9. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Migration Pathways – Re-Host

10. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Migration Pathways – Re-Host
Emulated Mainframe Environment Vendors
 Micro Focus Enterprise Server
 TMaxSoft Open Frame
 Oracle Tuxedo ART
Cost Optimize: Neutral
Improve Agility: Increase
Reduce Technical Debt: Improve

11. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Migration Pathways – Re-Purchase
UK-based bank lending to small and medium
enterprises
We are very confident in AWS’s proposition;
it has state-of-the-art technology, a
worldwide presence, a large number of
security certifications, and because of its
scale, is able to invest in information security
beyond what we’d be able to do on our own.
Francesca Gandolfo
Chief Operating Officer

12. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Migration Pathways – Re-Purchase
Cloud Native Banking Vendors
 Mambu
 Ophen
 EdgeVerve Finacle
Cost Optimize: Improve
Improve Agility: Increase
Reduce Technical Debt: Remove

13. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Migration Pathways – Re-Platform

14. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Migration Pathways – Re-Host
Cost Optimize: Improve
Improve Agility: Increase
Reduce Technical Debt: Remove
Re-hosting Bound by Technical Constrains
 Platform
 Runtime
 Database on-prem vs Cloud

15. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Migration Pathways – Re-Factor
The Strangulation Pattern
“…rewrite on an important system…”
“..gradually create a new system around the
edges of the old, letting it grow slowly over
several years until the old system is
strangled.
Martin Fowler
June 29, 2004

16. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Strangulation Strategy
”The Core”
Major BU App
Major BU App
Point App Point App
Point App Point App
Common Integration Layers Point App Point App
Major BU App Major BU App Point App Point App

17. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Strangulation Strategy
”The Core”
Major BU App
Major BU App
Point App Point App
Point App Point App
Common Integration Layers Point App Point App
Major BU App Major BU App Point App Point App

18. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Migrating the first Mainframe Application
 Largely Standalone – no deep integration with other systems
 Often build on Mainframe out of habit
 Great candidate for first experiment (i.e. Non Transactional)

19. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Strangulation Strategy
”The Core”
Major BU App
Major BU App
Point App Point App
Point App Point App
Common Integration Layers Point App Point App
Major BU App Major BU App Point App Point App

20. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Migrating significant Mainframe capability

21. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Migration Pathways – Re-Factor
Cost Optimize: Big Improvement
Improve Agility: Increase
Reduce Technical Debt: Big Decrease
Re-Factoring Bound by Technical Constrains
 Capability
 Build vs Buy

22. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Customer First Strategy: ISV and Partners

23. Thank You