The document discusses lessons learned during the cloud transformation of large financial institutions, focusing on architecture, technology, processes, and organizational culture. It emphasizes the importance of efficient IT, collaboration among teams, and adopting a DevOps mindset for successful cloud migration. Ultimately, the key to ongoing improvement and adaptation lies in strong communication, transparency, and the involvement of all stakeholders.

1. Going Cloud Native
Scars and all
Photo by Vladimir Anikeev on Unsplash

2. David Schmitz
How can we execute a Cloud
Transformation successfully?

3. @koenighotze
David Schmitz
https://de.wikipedia.org/wiki/Schlangen%C3%B6l

4. @koenighotze
David Schmitz
Impossible!
https://de.wikipedia.org/wiki/Schlangen%C3%B6l

5. @koenighotze
David Schmitz
Impossible!
Super easy! Barely an
inconvenience
https://de.wikipedia.org/wiki/Schlangen%C3%B6l

6. Some things learned while moving large financial institutes
into the public cloud

7. Some things learned while moving large financial institutes
into the public cloud
Architecture, tech, processes and culture and organisation

8. Some things learned while moving large financial institutes
into the public cloud
Architecture, tech, processes and culture and organisation
What worked for us, what may work for you

9. Some things learned while moving large financial institutes
into the public cloud
Architecture, tech, processes and culture and organisation
What worked for us, what may work for you
Each topic could be a whole workshop or project

10. @koenighotze
David Schmitz
David Schmitz
CTO @ Senacor Technologies
Coding architect with focus on cloud
and engineering efficiency

11. David Schmitz
Stepping back
Reasons to migrate to the cloud

12. David Schmitz
Efficiency

13. David Schmitz
We don’t know what the customers
really want

14. David Schmitz
We don’t know what the customers
really want
Fast iterations are the only way to
validate hypotheses

15. David Schmitz
We don’t know what the customers
really want
Fast iterations are the only way to
validate hypotheses
Our businesses are only as strong and
fast as their IT

16. @koenighotze
David Schmitz
Slow and
inefficient IT
Ideas
Production

17. @koenighotze
David Schmitz
Slow and
inefficient IT
Ideas
Production

18. @koenighotze
David Schmitz
Slow and
inefficient IT
Ideas
Production
The IT must be efficient if we want to
stay competitive!

19. @koenighotze
David Schmitz
Home-
grown
e2e IT
Focus on
essentials
Custom
Cloud,
SaaS
Classic
IT

20. @koenighotze
David Schmitz
Custom
Cloud,
SaaS
Classic
IT
How does implementing a load
balancer improve our business?

21. @koenighotze
David Schmitz
Cloud
Transformation
Blocks
Architecture
Technology and
Tooling
Data
Security,
Compliance and
Governance

22. @koenighotze
David Schmitz
Cloud
Transformation
Blocks
Architecture
Technology and
Tooling
Data
Security,
Compliance and
Governance
Culture and
Organisation

23. Photo by Markus Spiske on Unsplash
“Marie Kondo” your IT
Photo by Markus Spiske on Unsplash

24. @koenighotze
David Schmitz
Re-architect
Retire
Replace
Lift-and-Shift

25. @koenighotze
David Schmitz
Re-architect
Retire
Replace
Lift-and-Shift

26. @koenighotze
David Schmitz
Re-architect
Retire
Replace
Lift-and-Shift

27. @koenighotze
David Schmitz
Re-architect
Retire
Replace
Lift-and-Shift

28. @koenighotze
David Schmitz
Re-architect
Retire
Replace
Lift-and-Shift

29. @koenighotze
David Schmitz
Re-architect
Retire
Replace
Lift-and-Shift

30. @koenighotze
David Schmitz
Effort
Effectiveness

31. @koenighotze
David Schmitz
Effort
Effectiveness
The proper approach depends on your strategy and goals.
There is no “best” answer - context matters
?

32. @koenighotze
David Schmitz
In the end
it probably
will be a
hybrid
approach

33. @koenighotze
David Schmitz
Fast moving
cloud native
products
Slower moving
on-prem assets
In the end
it probably
will be a
hybrid
approach

34. @koenighotze
David Schmitz
The cloud native
products will
require changes
to the on-prem
assets
BUT!

35. @koenighotze
David Schmitz
Network
Access control
APIs
Availability
…
BUT!

36. Trap: two speed-IT

37. Trap: two class-IT

38. @koenighotze
David Schmitz
Cloud
On-Prem
Speedboat
Agile
Modern
Forwards
Tanker
Waterfall
Legacy
Backwards

39. @koenighotze
David Schmitz
What we want and need

40. @koenighotze
David Schmitz
What we want and need
Collaboration

41. @koenighotze
David Schmitz
What we want and need
Collaboration
Expertise

42. @koenighotze
David Schmitz
What we want and need
Collaboration
Expertise
End-to-End ownership

43. @koenighotze
David Schmitz
What we get instead

44. @koenighotze
David Schmitz
What we get instead
Resentment

45. @koenighotze
David Schmitz
What we get instead
Resentment
Non-commitment

46. @koenighotze
David Schmitz
What we get instead
Resentment
Non-commitment
Sabotage

47. @koenighotze
David Schmitz
Effort
Effectiveness
Impact on organisation as the
3rd dimension

48. @koenighotze
David Schmitz
Effort
Effectiveness
Impact on organisation as the
3rd dimension

49. Bring everybody to the table, cloud
experts, on-prem experts,…
https://unsplash.com/@akson

50. @koenighotze
David Schmitz
Bring everybody
on board

51. @koenighotze
David Schmitz
Bring everybody
on board
Re-train

52. @koenighotze
David Schmitz
Bring everybody
on board
Re-train
New roles

53. @koenighotze
David Schmitz
Bring everybody
on board
Re-train
New roles
New jobs

54. @koenighotze
David Schmitz
Bring everybody
on board
Re-train
New roles
New jobs
Mix teams

55. @koenighotze
David Schmitz
Bring everybody
on board
Re-train
New roles
New jobs
Mix teams
Be transparent

56. @koenighotze
David Schmitz
Bring everybody
on board
Re-train
New roles
New jobs
Mix teams
Be transparent
Offer perspectives

57. What skills do you need in a “Cloud
native” feature team?
https://unsplash.com/@priscilladupreez

58. David Schmitz
Why
DevOps?

59. David Schmitz
Why
DevOps?
Achieve best performance in
your software development
and delivery

60. David Schmitz
Why
DevOps?
Achieve best performance in
your software development
and delivery
Improve technical and cultural
capabilities

61. David Schmitz
Why
DevOps?
Achieve best performance in
your software development
and delivery
Improve technical and cultural
capabilities
Move towards a highly efficient
engineering organization

62. David Schmitz
s/Ops/DevOps/g

63. David Schmitz
s/DevOps/SRE/g

64. David Schmitz
Same job, only using Terraform?

65. David Schmitz
Adopting a DevOps culture and
mindset is key to becoming an
efficient software delivery organization

66. @koenighotze
David Schmitz
DevOps-based
full-stack
rockstar team

67. @koenighotze
David Schmitz
Java and SpringBoot
DevOps-based
full-stack
rockstar team

68. @koenighotze
David Schmitz
Java and SpringBoot
React
DevOps-based
full-stack
rockstar team

69. @koenighotze
David Schmitz
Java and SpringBoot
React
Testing with Gatling
DevOps-based
full-stack
rockstar team

70. @koenighotze
David Schmitz
Java and SpringBoot
React
Testing with Gatling
Gitlab Workflows
DevOps-based
full-stack
rockstar team

71. @koenighotze
David Schmitz
Java and SpringBoot
React
Testing with Gatling
Gitlab Workflows
Docker
DevOps-based
full-stack
rockstar team

72. @koenighotze
David Schmitz
Java and SpringBoot
React
Testing with Gatling
Gitlab Workflows
Docker
Really good and secure Docker
DevOps-based
full-stack
rockstar team

73. @koenighotze
David Schmitz
Java and SpringBoot
React
Testing with Gatling
Gitlab Workflows
Docker
Really good and secure Docker
Google Kubernetes Engine
DevOps-based
full-stack
rockstar team

74. @koenighotze
David Schmitz
Java and SpringBoot
React
Testing with Gatling
Gitlab Workflows
Docker
Really good and secure Docker
Google Kubernetes Engine
BigTable
DevOps-based
full-stack
rockstar team

75. @koenighotze
David Schmitz
Java and SpringBoot
React
Testing with Gatling
Gitlab Workflows
Docker
Really good and secure Docker
Google Kubernetes Engine
BigTable
Google Cloud SQL
DevOps-based
full-stack
rockstar team

76. @koenighotze
David Schmitz
Java and SpringBoot
React
Testing with Gatling
Gitlab Workflows
Docker
Really good and secure Docker
Google Kubernetes Engine
BigTable
Google Cloud SQL
Terraform and Terratest
DevOps-based
full-stack
rockstar team

77. @koenighotze
David Schmitz
Java and SpringBoot
React
Testing with Gatling
Gitlab Workflows
Docker
Really good and secure Docker
Google Kubernetes Engine
BigTable
Google Cloud SQL
Terraform and Terratest
Key Management
DevOps-based
full-stack
rockstar team

78. @koenighotze
David Schmitz
Java and SpringBoot
React
Testing with Gatling
Gitlab Workflows
Docker
Really good and secure Docker
Google Kubernetes Engine
BigTable
Google Cloud SQL
Terraform and Terratest
Key Management
…
DevOps-based
full-stack
rockstar team

79. @koenighotze
David Schmitz
Team A Team B Team C

80. @koenighotze
David Schmitz
Persistence
Security
CI/CD
…
Persistence
Security
CI/CD
…
Persistence
Security
CI/CD
…
Team A Team B Team C

81. @koenighotze
David Schmitz
Persistence
Security
CI/CD
…
Persistence
Security
CI/CD
…
Persistence
Security
CI/CD
…
Redundant effort
Team A Team B Team C

82. @koenighotze
David Schmitz
Persistence
Security
CI/CD
…
Persistence
Security
CI/CD
…
Persistence
Security
CI/CD
…
Redundant effort
Maintenance burden
Team A Team B Team C

83. @koenighotze
David Schmitz
Persistence
Security
CI/CD
…
Persistence
Security
CI/CD
…
Persistence
Security
CI/CD
…
Redundant effort
Maintenance burden
No shared knowledge
Team A Team B Team C

84. @koenighotze
David Schmitz
Persistence
Security
CI/CD
…
Persistence
Security
CI/CD
…
Persistence
Security
CI/CD
…
Redundant effort
Maintenance burden
No shared knowledge
No lessons learned
Team A Team B Team C

85. @koenighotze
David Schmitz
Persistence
Security
CI/CD
…
Persistence
Security
CI/CD
…
Persistence
Security
CI/CD
…
Redundant effort
Maintenance burden
No shared knowledge
No lessons learned
Autonomy gone haywire
Team A Team B Team C

86. Everybody loves K8S
Everybody hates debugging K8S
https://unsplash.com/@cdc

87. @koenighotze
David Schmitz

88. David Schmitz
Manifest learnings and
practises as
Infrastructure Products

89. @koenighotze
David Schmitz
Persistence
Security
CI/CD
…
Persistence
Security
CI/CD
…
Persistence
Security
CI/CD
…
Team A Team B Team C

90. @koenighotze
David Schmitz
Persistence
Security
CI/CD
…
Team A Team B Team C

91. @koenighotze
David Schmitz
CI/CD Runtime Security
Chaos Test Monitoring Persistence
Governance
…
The platform team builds products that
capture good-practises and lessons learned
Team A Team B Team C

92. @koenighotze
David Schmitz
CI/CD Runtime Security
Chaos Test Monitoring Persistence
Governance
…
Team A Team B Team C
The platform teams build products that
capture good-practises and lessons learned

93. Trap: Fix-it-fast-tiger-team

94. @koenighotze
David Schmitz
Team A Team B Team C
Eager
manager
Production

95. @koenighotze
David Schmitz
Team A Team B Team C
Eager
manager
Production
I NEED MY FEATURES
NOW! I DO NOT CARE
WHAT YOU HAVE BEEN
WORKING ON.
GET IT DONE ASAP!!!!
WOHA!!!! BUT FIRST FIX
AND OPTIMISE THE
PRODUCTION
MONGODB…FAST!
NO NO NO!!! WE WANT
TO USE RUST BECAUSE
IT IS NICE! SO BUILD
US A PIPELINE FOR
THAT

96. David Schmitz
Platform teams must be handled as any other feature
team with clear customer / producer relations
Builds
products
for
teams
Team B
Team A
Team C

97. David Schmitz
Starting with full-stack teams and
then migrating towards platform
teams combines learning and maturity
Team B
Team A
Team C
Platform team
Start of Cloud Journey

98. @koenighotze
David Schmitz
Don’t establish a hidden 2-class-IT
with the platform team

99. @koenighotze
David Schmitz
Team A Team B Team C
Cool new
tech
Only business
churn

100. @koenighotze
David Schmitz
Team A Team B Team C
Beware the platform bottleneck
Ideas
Ideas
Ideas

101. @koenighotze
David Schmitz
Team A
Instead: Inner-Source
Submit Pull Request
Go CI/CD
pipeline
Build
solution

102. But, we cannot do this with security, or
can we?
https://unsplash.com/@joshredd

103. @koenighotze
David Schmitz
Dev starts Prod rollout

104. @koenighotze
David Schmitz
Dev starts Prod rollout
Panicked
security fixing

105. @koenighotze
David Schmitz
Dev starts Prod rollout
Security is part of
Development

106. David Schmitz
DevSecOps
As with
operations, work
closely with
security experts
right from the
start and not as
an afterthought

107. @koenighotze
David Schmitz
New developer-
oriented security
tools bring new
opportunities

108. @koenighotze
David Schmitz
Most checks
can happen
as part of the
delivery
pipeline

109. David Schmitz

110. David Schmitz

111. David Schmitz
Apply the DevOps mindset to all
aspects of collaborative software
development

112. In closing
https://unsplash.com/@wflwong

113. David Schmitz
How do we know if we are
“there” yet?

114. David Schmitz
Mindset: There is no “there”, only
continuous improvement

115. David Schmitz
Deployment frequency
Lead time
MTTR
Change fail percentage
Move fast without breaking
everything all the time
4 key metrics
give guidance
and allow us to
measure
progress

116. David Schmitz
Deployment frequency
Lead time
MTTR
Change fail percentage
Especially without breaking our
culture and people

117. @koenighotze
David Schmitz

118. @koenighotze
David Schmitz
Organisation and culture
are the biggest
challenges

119. @koenighotze
David Schmitz
Organisation and culture
are the biggest
challenges
Rethink everything -
especially the processes

120. @koenighotze
David Schmitz
Organisation and culture
are the biggest
challenges
Rethink everything -
especially the processes
Build a relevant slice as
soon as possible

121. @koenighotze
David Schmitz
Organisation and culture
are the biggest
challenges
Rethink everything -
especially the processes
Build a relevant slice as
soon as possible
Assume best intend

122. David Schmitz
Cloud can release new energy in
development teams

123. David Schmitz
Cloud can release new energy in
development teams
Experimentation and continuous
improvement and learning

124. David Schmitz
Cloud can release new energy in
development teams
Experimentation and continuous
improvement and learning
Bring the best minds together and allow
the best idea to win

125. @koenighotze
David Schmitz

126. David Schmitz
It is all about the people

127. @koenighotze
David Schmitz
Thank you for your
attention and time!
David Schmitz
CTO / Partner Principal
M +49 (162) 4382 168
David.Schmitz@senacor.com