MODERNIZING IT WITH
MICROSERVICES
www.leanix.net
Simon Barth
simon.barth@leanix.net
Key Takeaways
2
Be able to reflect Microservices in your EA inventory &
see the chances for EA
1
Take the 1st steps of a Microservice transformation
Understand benefits of a Microservice architecture
2
3
3
We asked over 100 high-profile IT experts
about the usage, transformation and
challenges of Microservices
LeanIX Microservice Study 2017
80% of surveyed companies bet on microservices
4
We use mostly
microservices
9%
New
components
as
microservices,
old monoliths
maintained
38%
We intend to
transform
existing
monoliths to
microservices
33%
Microservices are
no option 20%
Does your company use Microservices?
Majority thinks still in long release terms
5
Max 1 per year
Multiple times per year
Multiple times per month
Multiple times per week 17%
24%
51%
8%
How often do you deploy new releases?
Companies who use microservices are much faster
6
Max 1 per
year
Multiple
times per
year
Multiple
times per
month
Multiple
times per
week
# RELEASES ‘NO MICROSERVICES’
Max 1 per
year
Multiple
times per
year
Multiple
times per
month
Multiple
times per
week
# RELEASES ‘MICROSERVICES’
Companies using microservices are faster
We will see a spike in microservice usage in 2017
7
71%
1/3 does not have planned to
intensify their usage of
microservices in 2017
29%
2/3 of companies will intensify
their usage in 2017
Do you plan to intensify the usage of Microservices?
Legacy processes & lack of knowledge are the
main hurdles that companies face
8
Politics
Higher complexity
Legacy processes
Missing knowledge & people
Microservices are no option
Intend to transform to microservices
New components as microservices, old monoliths maintained
11%
21%
33%
35%
What are the major hurdles for adopting Microservices?
One step back – microservices philosophy
9
Microservice architecture
10
Benefits of Microservices
11
Flexible TechnologiesAgile Teams
Rapid DeploymentFailure Tolerance
Transparency on responsibilities
• Easy information on members in charge
of Microservice
• Modern collaboration possibilities on
Microservice level
Why Microservices and EA?
• Complexity through high
granularity
• Challenging integration in
legacy software ecosystem
• Identifying spikes in over
network communication
between Microservices
• Providing agile teams easy
access to information about
Microservices (e.g.
responsibilities)
• Manage diverse
technologies
LeanIX SolutionsMicroservices Challenges
Smart Inventory
• Reliable overview and transparency
• Automatic updates of repository
Reports and metrics to plan
transformation
• Identification of problems
• Relations tracing and visualizations
Use Cases
13
• Automated Microservice repository
• Dependency management
• Responsibilities & roles
• Inter-Microservice request monitoring
• Monolith to Microservice roadmap planning
1
2
3
4
5
Automatic import from development environment
14
LeanIX Java SDK
Check if the
Microservice exists in
repository
Create a new
Microservice
Update existing
Microservice
or
Identify spikes in requests
15
What we learned along the way
16
Automation
Services <= Team size
Self-documented
REST APIS (e.g. swagger)
Don’t share data storage
Distributed verifcation
(e.g. oAuth2)
Getting started
17
Read the full LeanIX Microservices Study 2017 (leanix.net/downloads) and share it
with your colleagues
Today
Involve the right stakeholders and decide whether and how microservices could be
leveraged more at your company. Start a small pilot. Build your repository.
In the next three months
Drive larger scale projects to transform monoliths to a microservice architecture.
Make it a priority of your agenda
After that
Thank you.
18
Please get in touch!
simon.barth@leanix.net
+ 49-228 2862992-0
www.leanix.net

Modernizing IT with Microservices

  • 1.
  • 2.
    Key Takeaways 2 Be ableto reflect Microservices in your EA inventory & see the chances for EA 1 Take the 1st steps of a Microservice transformation Understand benefits of a Microservice architecture 2 3
  • 3.
    3 We asked over100 high-profile IT experts about the usage, transformation and challenges of Microservices LeanIX Microservice Study 2017
  • 4.
    80% of surveyedcompanies bet on microservices 4 We use mostly microservices 9% New components as microservices, old monoliths maintained 38% We intend to transform existing monoliths to microservices 33% Microservices are no option 20% Does your company use Microservices?
  • 5.
    Majority thinks stillin long release terms 5 Max 1 per year Multiple times per year Multiple times per month Multiple times per week 17% 24% 51% 8% How often do you deploy new releases?
  • 6.
    Companies who usemicroservices are much faster 6 Max 1 per year Multiple times per year Multiple times per month Multiple times per week # RELEASES ‘NO MICROSERVICES’ Max 1 per year Multiple times per year Multiple times per month Multiple times per week # RELEASES ‘MICROSERVICES’ Companies using microservices are faster
  • 7.
    We will seea spike in microservice usage in 2017 7 71% 1/3 does not have planned to intensify their usage of microservices in 2017 29% 2/3 of companies will intensify their usage in 2017 Do you plan to intensify the usage of Microservices?
  • 8.
    Legacy processes &lack of knowledge are the main hurdles that companies face 8 Politics Higher complexity Legacy processes Missing knowledge & people Microservices are no option Intend to transform to microservices New components as microservices, old monoliths maintained 11% 21% 33% 35% What are the major hurdles for adopting Microservices?
  • 9.
    One step back– microservices philosophy 9
  • 10.
  • 11.
    Benefits of Microservices 11 FlexibleTechnologiesAgile Teams Rapid DeploymentFailure Tolerance
  • 12.
    Transparency on responsibilities •Easy information on members in charge of Microservice • Modern collaboration possibilities on Microservice level Why Microservices and EA? • Complexity through high granularity • Challenging integration in legacy software ecosystem • Identifying spikes in over network communication between Microservices • Providing agile teams easy access to information about Microservices (e.g. responsibilities) • Manage diverse technologies LeanIX SolutionsMicroservices Challenges Smart Inventory • Reliable overview and transparency • Automatic updates of repository Reports and metrics to plan transformation • Identification of problems • Relations tracing and visualizations
  • 13.
    Use Cases 13 • AutomatedMicroservice repository • Dependency management • Responsibilities & roles • Inter-Microservice request monitoring • Monolith to Microservice roadmap planning 1 2 3 4 5
  • 14.
    Automatic import fromdevelopment environment 14 LeanIX Java SDK Check if the Microservice exists in repository Create a new Microservice Update existing Microservice or
  • 15.
    Identify spikes inrequests 15
  • 16.
    What we learnedalong the way 16 Automation Services <= Team size Self-documented REST APIS (e.g. swagger) Don’t share data storage Distributed verifcation (e.g. oAuth2)
  • 17.
    Getting started 17 Read thefull LeanIX Microservices Study 2017 (leanix.net/downloads) and share it with your colleagues Today Involve the right stakeholders and decide whether and how microservices could be leveraged more at your company. Start a small pilot. Build your repository. In the next three months Drive larger scale projects to transform monoliths to a microservice architecture. Make it a priority of your agenda After that
  • 18.
    Thank you. 18 Please getin touch! simon.barth@leanix.net + 49-228 2862992-0 www.leanix.net