I am talking about four key points, Application Architecture, Development method, Organizations and Cooperation, Operation and Maintenance, to consider in legacy modernization and what the end result should be. We think you'll understand why you should consider Red Hat's "open hybrid cloud" approach. Please take a look.

1. Why we should consider Open Hybrid
Cloud
14th June 2022
Masahiko Umeno
Chief Technologist, Red Hat K.K.
Open Hybrid Cloud Week 2022
1

2. Copyright 2022 Red Hat K.K.
2
Perspective in Legacy Modernize
We need to take an progressive thought more aggressively which
are in application architecture, development and so on when we
consider the IT supports the Business from now on.
1. Application Architecture
2. Development method
3. Organizations and Cooperation
4. Operation and Maintenance
Focus to 4 points

3. Application
Architecture
3

4. Copyright 2022 Red Hat K.K.
4
What Application we should Target?
写真・映像編集 基幹業務 生産管理 情報収集分析 機械学習
Package
Scratch
Development
Specialized for a specific
purpose
Operations that are no
different from other companies
Function/Operation that are central to
the company’s business that differ from
other companies
● Data
● Logic
● Process
● User Interface
● Integration
● User Management
● Security
● Integrity
● Load balance
● Operations
Video/Movie Core system
Production
Management
Gathering and
Analysis
AI/ML

5. Copyright 2022 Red Hat K.K.
5
A typical Mission Critical System in a company
Customer
Sales
Production Quality Assurance
Accounting
Product
Development
Web has uneven
access
Department-s
pecific codes
Huge volume of
Batch processing at
closing day
Shared DB
by all systems
Real work is
on Excel
(Shadow IT)
Similar many
logics
Cross-depart
mental
processing

6. Copyright 2022 Red Hat K.K.
6
What are Microservices?
User Interface Service
Process Service
Decision Service
Data Service
Integration Service
Platform Service
Infrastructure Service
In/Out to screen/paper
Progress Management for Biz
Check / Calc / Reasoning
Store / Retrieve
Service / Between System
Service running environment
Physical / Virtual environment
Registry Order Shipping Stock
Mgmnt
Sales Account
Business Functions
Service as IT x Domain = Microservices
Service as IT

7. Copyright 2021 Red Hat K.K.
7
Example of Microservices Implementation (Order)
Contract DB
Processing
Access
External
Services
Retrieve
Data
Store Data
Java Java+
Rule Engine
Java+
Rule Engine
Java
Java
Dispatcher
Java
Tagging for each
processing
Waiting
List
Queue
Java
Increase throughput with
multiple running
Waiting
List
Queue
External
Services
Contract DB
Processing
Result
Queue
Other
services
Container
Tagging
Subscribe
Subscribe
DataBase DataBase
Order Data
Microser
vices

8. Copyright 2022 Red Hat K.K.
8
Relevant with Microservices and Platform
Not microserviced system
Infrastructure
Parts
expansion
Aggregation
by buyer
Aggregation
by product
Aggregation
by Supplier
Aggregation
by Parts
Calculate
Delivery
date
UI for
Quotation
UI for
Delivery
Date
● Multiple functions integrated into
one application
● Modification effort is the same as
before
● Uneven resource usage
● Difficult load balancing efficiently
● 1+1 HA configurations
● Almost same as a Virtual Machine
Environment
Worker Node
OpenShift Container Platform
Infra Node Worker Node Worker Node Worker Node
RHEL
Infrastructure

9. Copyright 2022 Red Hat K.K.
9
Relevant with Microservices and Platform
Microserviced system
Choosing container is the best in order to maximize effort of development/deploy microservices
applications. When ensure performance that is needed by increase multiplexing running, auto scale
out/in is useful.
Parts
expansion
Worker Node
OpenShift Container Platform
Infra Node
Parts
expansion
Parts
expansion
Aggregation
by Parts
Aggregation
by Supplier
Aggregation
by buyer
Calculate
Delivery
date
Aggregation
by product
Infrastructure
UI for
Quotation
UI for
Quotation
UI for
Delivery
Date
UI for
Delivery
Date
Worker Node Worker Node Worker Node
RHEL
Infrastructure

10. Copyright 2022 Red Hat K.K.
10
Edge Computing
Wide bandwidth
and not expensive
Narrow bandwidth
and expensive
Processing near the source of the data
Private Cloud
Private Cloud
Private Cloud
Mother Cloud
Deploy and running same
application with massive numbers
Manage deploying applications
High workload like an analysis
Hybrid Cloud
Environment

11. Development
Method
11

12. Copyright 2022 Red Hat K.K.
12
Choice of development methodology
Waterfall Agile/Scrum
Any appropriate Development
method?
Any criteria to consider?
● Past experiences
● Audit Standard
● ...
● Type of Application
● Scale of project
● Application Architecture

13. Copyright 2022 Red Hat K.K.
13
Type of Application
Create and deploy a brand new application
Any method are available. However there are no applications which
has immutable requirement from project start to release. Thus the
iterative development method is useful.
Renewal a legacy system
• If you take even unused source code, it does not know what the renewal
is for. Take only what you use or the cost will up extremely.
• Virtually impossible to discard specification from the source code only.
• ML uses real data to find logic. Migrate required logic with “Human
notice” using real data and result of test.
• Iterative development let you bring more better production quality.
• Migrate data with appropriately integration and test.

14. Copyright 2022 Red Hat K.K.
14
Scale of Project
The larger the system, the less realistic it is to estimate the details
Then, it is better to organize small and multiple projects aligned
business domain.
Due to increase quality, take the iterative development
● Omit unnecessary logic / data
● Resolve performance issue at early stage
● Reduce risk with deploying success experiment
● Use cloud env. which are familiar by each system
integrator, but provide a unified container env.
as taking same architecture.
https://www.redhat.com/ja/enga
ge/successful-legacy-modernizati
on-s-202201280548

15. Copyright 2022 Red Hat K.K.
15
Application Architecture
● Test used to be a backward process if you take an monolithic
architecture, however more effective is to test in iterative
development from early stage
● Design, Development and Test are enable iteratively for each
service unit when taking a microservices architecture
Iterative development is possible with either architecture,
priority should be given to improving quality

16. Copyright 2022 Red Hat K.K.
16
Application Modernization and Development
- Application perspective correlation
Iterative
Development
Test Driven
Development
Microservices
Architecture
Rule
Driven
Develop
ment
UI Service
Process Service
Decision Service
Data Service
Integration Service
Platform Service
Organize Domains
Definition as
IT Service
Suppress FAT DB
Agile
Scrum
Build Analysis
Test
Container
Image
Push
Image
Deploy
to Dev
Analysis
Unit
Test
Deploy to
STAGING
Continually integration(CI) Continually deployment(CD)
Result of
Current App
Result of
New App
NG: Missing Logic or Data, Bug, Conflict
Input Data
Current App New App
Q
Q
Asynchronous, multiprocessing,
de-Batch, Data pipeline
Container Env
Container Env.
Quarkus
Serverless
Clear focuspoint, Resolve issue by conversation
with business user
Test Driven Development
Container Env.
&
API
API Mgmt
Migration
Plan
Sales
Data from past N year
or
Prepared data
Optimize granularity
Establish new
business
Stock
Shipping

17. Copyright 2022 Red Hat K.K.
17
Iterative is the best development methodology
Implement application for small scale domain with microservices
● Define overall design (the trunk)
● Develop and test data, logic, UI, integration, etc by
each team
● Complete the implementation, like an expanding to
the branches and leaves.
● Unified development, operating, and testing
environments are required
Container env. Is suitable for iterative development

18. Copyright 2022 Red Hat K.K.
18
Why do you still insist on Waterfall?
● New technologies and methods are perceived as risky
● Avoid confusion due to additional requirements
● Accounting standard apply to only completion products
● Lack of analysis on past projects
● Failure will affect my career...
Without (excessively) pursuing responsibility
Change the culture to one where hardships and causes
can be learned as knowledge
Allow for gradual change rather than abrupt change

19. Organization and
Cooperation
19

20. Copyright 2022 Red Hat K.K.
20
Organization relations
Business
IT Div.
System Integrator
Gaps create
discrepancies
Hierarchy
creates
responsibility
issues
Typical
● One tier down to be involved.
● IT department is treated as middle
management
● Subordinate organizations are forced to
receive absurd requests
● Difficult to offer advice, etc., outside of
one's own role
● Multiple contracting occurs at a system
integrator
● It becomes a message game when a
problem occurs, and it takes time to solve
it
● Applications are created just to work,
without adhering to architecture and
development methods
etc...

21. Copyright 2022 Red Hat K.K.
21
Challenges of iterative development in a traditional
organization
Difficult conversation with business units (Voice from IT)
● You know that don’t you?
● There is existing invisible and intense hierarchical relationship that makes them
reserved
● They say they don't see the benefit of having their time taken up by something
other than their own work
● First of all, how much it will cost over all?
Difficult conversation with IT division (Voice from Biz)
● Can’t understand explanation in technical terms
● Why not just put in a package? We don't do anything special (what we do in our
company is common knowledge in the world)
● Why does it take so long when I can do it right in Excel?
● I can only come up with requirements based on the assumption the current system

22. Copyright 2022 Red Hat K.K.
22
Organization relations
Business
IT Div
System Integrator
Business
IT Div
System
Integrator
Ideal
By gradually advancing iterative development, we can advance to the ideal
Typical

23. Copyright 2022 Red Hat K.K.
23
From our experience
Study session by Biz
Diagram the
data and logic
Implement, Test
Review,
Define target
Deploy
● Understand their business
outline at Study session
● Diagram the data and logic
● Implement, Test, Review,
Define next target
Checked source code at the end
Minimize man-hours and maximize quality
Request cooperation to Biz

24. Copyright 2022 Red Hat K.K.
24
Organization and Role
● Ask the other System Integrator instead of the current
● IT should propose to Biz as an equal
● Create small group in Bis and IT, try to make runnable something, and
then test it, discuss it, rivise, and repeat it
● Require Architecture, tool, environment that are useful to biz agility
● Prepared environment where function and load test can be done with
real data as soon as it created
● Prepared environment which can use data and applications on
on-premise and cloud, either on container
Stakeholders naturally come together and cooperate
with each other

25. Operation and
Maintenance
25

26. Copyright 2022 Red Hat K.K.
26
Quickly provide a unified development environment with
containers
Same development environment is provided from anywhere,
even library versions
● Reduce the verification of differences in behavior due
to different environments
Provide an environment of self service preparation, rather
than requieting and waiting several days
● Reduce waiting time that environment build
● Reduce waiting time for load test
● Enable high quality test like Blue / Green Test or Canaria Release rather than
current
● Better checking of marginal performance

27. Copyright 2022 Red Hat K.K.
27
Fault Tolerance through microservices
Waiting
List
Queue
Java
… Waiting
List
Queue
Java
… Waiting
List
Queue
Waiting
List
Queue
Error
Data
Queue
Java
…
Acceleration by multiplexing
Portability to avoid failures

28. Copyright 2022 Red Hat K.K.
28
Relevant with Platform
Production Test
BCP
When system trouble occur on that
environment, all application will stop if you
depend on 1 environment
Need several container env. That can run the same app in
multiple cloud environments.
Open Hybrid Cloud is the BEST

29. Conclusion
29

30. Copyright 2022 Red Hat K.K.
30
Conclusion
Microservice
Architecture
Iterative Development
Utilize on-premise and
cloud environment
Cooperate with Biz and
IT
Event Driven
Application
Repeatable
development and Test
CI / CD
Prioritise
Review test result
Business Simulation
Dev Organization / BCP
/
Issue reproducer
Application
Architecture
Development
Method
Organization and
Cooperation
Operation and
Maintenance
Application
Development
&
maintenance
Container
Hybrid Cloud
Container
Container
Container
Hybrid Cloud

31. Copyright 2022 Red Hat K.K.
31
Considering not only development but also operation of future
applications and platforms, the destination is
Hybrid Cloud
Red Hat is offering Open Hybrid Cloud.

32. linkedin.com/company/red-hat
youtube.com/user/RedHatVideos
facebook.com/redhatinc
twitter.com/RedHat
THANK YOU
Red Hat is the world’s leading provider of enterprise
open source software solutions. Award-winning
support, training, and consulting services make
Red Hat a trusted adviser to the Fortune 500.