traditional to cloud shift

1. Traditional to Cloud Shift :
When to integrate and when not to
Gunnar Menzel
Telford, September 27th
#CWIN17

2. The Traditional to Cloud Shift | 27th Sep 2017
Copyright © 2017 Capgemini and Sogeti. All rights reserved. 2
Table of Contents
1. The Cloud-native opportunity
2. The Shift Challenges
3. The Shift Approach

3. The Traditional to Cloud Shift | 27th Sep 2017
Copyright © 2017 Capgemini and Sogeti. All rights reserved. 3
The Cloud Opportunity
“15% of new apps are cloud native, moving towards 30% by 2020”
cloud_native_comes_of_age.pdf
15%
today
32%
2020

4. The Traditional to Cloud Shift | 27th Sep 2017
Copyright © 2017 Capgemini and Sogeti. All rights reserved. 4
The Cloud Question
“For many it is decision time”
 Should I move all traditional to cloud native?
 If yes, how?
 If no, why not?

5. The Traditional to Cloud Shift | 27th Sep 2017
Copyright © 2017 Capgemini and Sogeti. All rights reserved. 5
Define Traditional and Cloud Native
“Traditional and Cloud explained”
Cloud
Traditional Applications Cloud-native Applications
Infra / Middleware
Environment
Apps designed, developed
and built and run on premise
Built to run optimally on cloud / as-
a-service infra and middleware
Model
• SOA
• Organised around technology
layers – three-tiered
• State in each runtime
instance
• One stack for the entire app
• Microservices
• Can deploy each microservice
independently
• Organised around business
capabilities
• Choice of technology for each
microservice

6. The Traditional to Cloud Shift | 27th Sep 2017
Copyright © 2017 Capgemini and Sogeti. All rights reserved. 6
The Shift Considerations
“Aspects to consider when deciding to shift”
Business Case 1
Moving from traditional to cloud-native must
follow a proper business case the move to cloud
is not always providing benefits.
On-premise traditional IT2
Successful cloud might requires well-architected
private cloud.
Security 3
Ensure you are covering all aspects from user
identification, authorisation and authentication, to
data and network encryption, intrusion detection
Networking4
Latency and bandwidth issues, chatty
applications, network topology, network security,
extending local topology to the cloud
Data and Application Integration 5
Throttling of inbound queries, data move,
interdependencies and impact of remote host is
not necessary available
Cloud is not = Cloud 7
Treat your cloud provider selection like a COTS
selection. Each cloud provider will have very
different characteristics covering SLA, APIs,
People8
Cultural shift for people, skills are in high demand,
so difficult to find, require architecture skills.
Service, Release & Change Management6
Configuration management, patching, capacity
planning and monitoring, system monitoring etc

7. The Traditional to Cloud Shift | 27th Sep 2017
Copyright © 2017 Capgemini and Sogeti. All rights reserved. 7
The Shift Challenge
“Capgemini survey findings”

8. The Traditional to Cloud Shift | 27th Sep 2017
Copyright © 2017 Capgemini and Sogeti. All rights reserved. 8
The People Shift
“3 dimensions to consider”
Shift Left
ShiftUp
3TechnologyStack
Network
Applications
Middleware
Compute
Storage
ImplementBuildDesignDefinePlanStrategy Run
2 Software Lifecycle
Shift Right
SectorCollaborateRisk TakerSolverLearnerInnovate Present
1 Skills

9. The Traditional to Cloud Shift | 27th Sep 2017
Copyright © 2017 Capgemini and Sogeti. All rights reserved. 9
The People Shift
“3 dimensions to consider”
Shift Right
1 Skills
Innovate
displays self-awareness
and reflection; seeks
active feedback and
applies new behaviours;
Learner
actively seeks new
knowledge; finds new
ways of addressing
today's challenges
Solver
displays curiosity and
likes to experiment; open
to change and challenge
the status quo;
Risk Taker
can tolerate ambiguity
and complexity; and
remain resilient through
adversity; positive thinker;
Collaborate
actively seeks
engagements, happy to
share views & material,
sees opportunities
Sector
understands the sector
he/she is working in, can
identify & shape business
value propositions
Present
happy to present and
communicate to different
stakeholder groups ;

10. The Traditional to Cloud Shift | 27th Sep 2017
Copyright © 2017 Capgemini and Sogeti. All rights reserved. 10
The Shift Approach
“6 Steps”
1. Assess
 Assess the application portfolio and identify priorities for cloud-native development
2. Leadership
 Build credibility with the CEO and line of business leaders by demonstrating a cloud roadmap and ability to deliver
growth
3. Step-by-Step
 Start small, and then scale up to develop a skilled team
4. Target Operating Model
 Adapt the IT operating model to support both business agility and stability
5. Be pragmatic
 In selecting technologies : lock-in risks and integration challenges are not insurmountable
6. Culture
 Incubate a culture of innovation, collaboration, testing and learning

11. The Traditional to Cloud Shift | 27th Sep 2017
Copyright © 2017 Capgemini and Sogeti. All rights reserved. 11
Thank You!
Phone: +44 7891153325
Gunnar.menzel@capgemini.com
Gunnar Menzel
Chief Architect
gunnarmenzel