Most people think digital transformation is daunting, especially when you start with monolithic legacy systems, but it doesn’t have to be.
This webinar focuses on five practical steps you can take to get started on your legacy integration journey. These steps minimize the drag on various IT teams while offering a noticeable impact in supporting your DevOps process and overall company.
You’ll learn how to avoid the cost, risk, time and resources normally associated with legacy modernization. Legacy integration experts Zeev Avidan and Martin Bakal from OpenLegacy also share real-life DevOps driven transformation successes as they walk you through:
Rethinking digital transformation so it’s less complex
Tips for getting started without overwhelming yourself or others
Simple steps to incorporate your on-prem systems into DevOps
Fast and easy test and deployment strategies
Demo of how to quickly do a digital transformation with your legacy assets
Five Ways to QuickStart a Digital Transformation Project
1. Five Way to QuickStart a Digital
Transformation Project
www.openlegacy.com
#OpenLegacy
2. Agenda
• Rethinking digital transformation
• Steps to incorporate your on-prem systems
• Test and deployment strategies
• Real-life samples - DevOps driven transformation
• Demo
• Questions and answers
#OpenLegacy 2
6. Examples of enterprises that jumped right in
6
● An insurance company created 100 APIs in 2 months.
○ Saved total development time of about 1 full year of man-hours
● A bank deployed 27 new APIs, with more than 70 microservices in 10 weeks.
● Creating an API in less than an hour - compared to 1-2 months previously.
#OpenLegacy
8. 1. Get started with limited resources
8
Why are legacy team members normally
required?
• Analysis
• Data type translation
• Building facades
Legacy team members are a
limited resource. To keep teams
small, don’t require them!
#OpenLegacy
9. Transformation without legacy team members/systems
9
You gain:
• Flexibility
• Resource Availability
• Fewer approvals needed
OpenLegacy achieves this by:
• Automatic parsing
• Java
• Direct connection
Result: Teams can move between
cloud and hybrid integration projects.
#OpenLegacy
10. 2. Start with an MVP
10
Skew tradeoff decisions towards the
strategic.
Pick a pain point from the organization:
• Impactful to stakeholders
• Easily definable
Automatic parsing simplifies the
monolith—the team can pick the content
Simplifies the integration scenario and
allows teams to get started
GOAL
Not have IT be a bottleneck
USE CASE
New deal with large bank
• Sell to their business customers
• Software updates completed 2 months
before signed agreement
SOLUTION
Legacy
Integration
#OpenLegacy
DevOps
12. 3. Build connections to legacy quickly and easily
12
This might look daunting:
• Design the API
• Build the facade
• Streamline communication
• Retrofit deployment environment
• Build on proprietary processes
But automation makes the process simpler:
• Exposes potential APIs
• Generates connecting code
• Direct Connections speed execution
#OpenLegacy
13. 4. Automate test generation
13
Testing Process
A typical process build:
Test Driven Design (TDD)
OpenLegacy automates:
Testing Integration
Regression
Unit
Deployment
#OpenLegacy
14. 5. Simplify deployment
14
Bringing legacy data to the cloud
• Microservices ease deployment
• OpenLegacy generates Docker with
binding, a configured Gateway
• Simplified process
Microservices make DevOps deployment
work
#IBMi
Deploy anywhere with
microservices architecture
“Architects have grown accustomed
to thinking that robustness equals
complexity. OpenLegacy
demonstrates the other way is true.”
— Senior Architect
“Simplified our architecture to
deploy faster and more efficiently.”
— Creditcorp
#OpenLegacy
15. Modernize with a Scalable Microservices and API Integration
Legacy
and on-prem
systems &
applications
1
Automatic generation of
SDK
(standard Java code)
2
Design the API using
Point-and-Click or
Open Java code
3
One-click deployment of
microservices applications
4
Digital services rollout
Using DevOps
standards
5
#OpenLegacy 15
16. DEPLOY
Swagger Spec /
Microservice /
API Gateway
OpenLegacy API Contract
Console for:
• Analytics
• Optimizations
• Security
Dependencies API
API
Contract
Orchestration /
Transformation
OpenLegacy SDK 1
OpenLegacy SDK 2
OpenLegacy SDK N
Entity MetaData 1
OpenLegacy SDK
Entity MetaData 2
Connection
Properties
Entity MetaData N
Connector
OpenLegacy
Front End
Structure
Generation
Legacy
System
DEMO / Create and Run Mainframe API
Angular
Application
Optionally manual
Metadata Model
Generation
Structure
Generation
Contract
Generation
Automated
MS Deploy
Automated
Front End
OL
Wizards
#OpenLegacy 17
17. Getting steered in the right direction with these offers
18#OpenLegacy
Schedule a personalized demo
https://go.openlegacy.com/devopsdemo
Schedule a Proof of Concept (PoC)
https://go.openlegacy.com/devopspoc
18. Q&A
Wrap-up and Q&A
18
1. Get started with limited resources
2. Start with an MVP
3. Build connections to legacy quickly and easily
4. Automate test generation
5. Simplify deployment
#OpenLegacy
20. It is not the strongest that survive but
the ones most adaptable to change
- Charles Darwin
Why Digital Transformation is Critical
20
21. DevOps
21
The topics discussed here aren’t just for
organizations moving to DevOps.
They are exacerbated by DevOps usage:
• Quick releases
• Testing
The general concepts are useful for any
methodologies.
SOFTWARE
PROCESS
DevOps is a spectrum.
#OpenLegacy
22. OpenLegacy Platform
Private Cloud, Public Cloud, or On-Prem System
Management Console
Analytics
High
Availability
Performance Security Discovery
DevOps CI/CD
Communicate
Automatic Generation of Microservice based APIs
Templates
API
Gateway
Cloud
Fetch Parse Automate
Java Microservice API SDK
EJB
Mobile
Web
REST
API
Mainframe
IBM i
Database
s
SOAP
JSON
#Openlegacy 22