SAP Inside Track 2018 - "Quidquid agis, prudenter agas ..." - Learnings from a transition from on-prem to cloud native
Download as PPTX, PDF3 likes773 views
The document discusses the transition from on-premise to cloud-native environments, emphasizing the importance of organizational culture and mindset alongside technology. It provides insights and advice for various roles such as product management, architects, developers, and operations teams to embrace continuous learning and collaboration. The author highlights that successfully leveraging cloud-native technologies requires breaking down silos and fostering a culture of innovation and iterative development.
SAP Inside Track 2018 - "Quidquid agis, prudenter agas ..." - Learnings from a transition from on-prem to cloud native
- 1. Quidquid agis, prudenter agas et respice finem My Learnings from aTransition from On-Premise to Cloud Native
- 2. About me ▪ Working in SAP ecosystem for 12 years ▪ On the cloud native journey … @lechnerc77
- 3. Where do we come from? ▪ On premise ▪ ABAP ▪ Monoliths that have grown over decades
- 4. Where do we (want to) go Cloud Native to leverage all promises of the cloud like: ▪ Scalability & Resilience ▪ High flexibility ▪ Fast release and feature cycles ▪ Reduction of on-premise pain
- 5. It is all about technology
- 6. … and techies go
- 7. But is your organization, the culture in your organization and the mindset of the people able to leverage what technology enables?
- 8. It is all about technology … really? Product Management Architects Test Engineers Developers Operations Sales …
- 9. “Whoever fights monsters should see to it that in the process he does not become a monster. And if you gaze long enough into an abyss, the abyss will gaze back into you.” Friedrich Nietzsche
- 10. The Challenges you might underestimate Technology Your on-premise Organization Culture Mindset
- 11. My experiences to deal with the challenges …
- 12. Flow from the past Define/Architect/ Design Develop Release
- 13. Flow we should achieve It is all about learning and adoption in fast iterations as a team Define/Architect/ Design Develop Release Reflect/Learn
- 15. Product Management - Advices ▪ Learn, Learn, Learn – like Domain Driven Design ▪ Show benefits of incremental development ▪ Push them to collaborate with the end user ▪ New answers needed like “How do we monetize our product?”
- 17. Architects - Advices ▪ Learn, Learn, Learn – Concepts ▪ Align with the fast iterative cycle – no big upfront architecture ▪ Architecture lives … in the team ▪ Base your decisions on data – “experiments”
- 18. Evolutionary Architecture “An evolutionary architecture supports guided, incremental change across multiple dimensions.”
- 20. Development - Advices ▪ Learn, Learn, Learn – especially outside the SAP ecosystem ▪ Select the (first) team wisely – mindset and comfort zone ▪ Do not get paralyzed by new stuff: one step at a time ▪ You are not the first Cloud Native Developers – Use the Ecosystem Get support and coaching
- 21. Development - Advices ▪ Do not go for polyglot programing at first ▪ Adopt Cloud NativeThinking: – Errors are okay, as long as you learn: faster/shorter cycles – Enable operations – “Automate everything” – “Continuous Everything”
- 22. Test Engineers
- 23. Test Engineers - Advices ▪ Learn, Learn, Learn - Methodology ▪ Respect the test pyramid ▪ Integrate testers in your team - collaboration ▪ You have new ways to test: “Test in production” (FeatureToggles, A/B testing)
- 25. Operations - Advices ▪ Learn, Learn, Learn – Continuous Everything ▪ Take the fear that they will be unnecessary in future – focus shift ▪ Integrate ops engineers into your team - collaboration ▪ Encourage developers for ops tasks – there might be hidden gems
- 26. Sales ▪ Every asked yourself how those folks get incentivized in the on-premise world? ▪ Cloud offerings are expected to be low-touch in every dimension ▪ How to bring this together?https://www.spreadshirt.com/commercial+sales+manager-A108280367
- 27. Essential “New” Role Security Engineer – this one is essential!
- 28. Summary ▪ Cloud Native is much more than technology ▪ Challenge: change of organization, culture and mindset ▪ Collaboration is king – bring all folks together & break silos ▪ Continuous learning is essential ▪ Fast cycles – take them as a chance not as a burden ▪ Take one step after another ▪ Learn beyond the SAP horizon
- 29. Questions?
- 30. Thank you for your attention!
- 31. Helpful Resources (completely biased) ▪ Rich and affordable source of books, webinars etc: https://www.safaribooksonline.com/ ▪ Watch conference contributions available onYouTube like: – GOTO: https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA – Devoxx: https://www.youtube.com/channel/UCCBVCTuk6uJrN3iFV_3vurg – Spring Developer: https://www.youtube.com/channel/UC7yfnfvEUlXUIfm8rGLwZdA – Cloud Foundry: https://www.youtube.com/channel/UC0ZYS0Y7b5oiVLvxGf4magw ▪ Embrace the Spring Ecosystem: https://spring.io/
- 32. Helpful Resources (completely biased) SAP ecosystem first choice – S/4HANA Cloud SDK https://www.sap.com/developer/topics/s4hana-cloud-sdk.html
- 33. Helpful Resources (completely biased) Follow the Cloud Native Ninjas like: – Sam Newman: @samnewman – Josh Long: @starbuxman – Kenny Bastiani: @kennybastian – Kelsey Hightower: @kelseyhightower – Pat Kua: @patkua – Jez Humble: @jezhumble – Eugen Parachiv: @baeldung
Editor's Notes
- #5: Not lift and shift Goal: Cloud Native SaaS Offering in Public Cloud
- #11: All the stuff is not explicitly restricted to the cloud, but here it becomes inevitable
- #12: This is not only valid for the cloud, but in the cloud this gets essential to survive
- #13: Errors are good – as long as you learn from them! Culture that encourages this! Get Feedback often and early
- #14: Errors are good – as long as you learn from them! Culture that encourages this! Get Feedback often and early
- #16: Past Godfathers of the product “We know what the customer wants” Thinking in relational DB models Thinking in long development cycles and big releases “It was always this way” is not an argument
- #18: Past Godfathers of technology Make the important architectural decisions upfront Experience driven decisions “Doing the hardest work, paving the way for development”
- #19: Incremental Change – Make changes in small increments Guided – Take into account prioritized cross-functional requirements + characteristics + avoid degrading Dimensions – Impacting factors beyond technological decisions like evolvement of data, security, Operations
- #21: Past Development in SAP NetWeaver ABAP was quite static compared to other areas Developers might be hibernated by organization Experience is based on on-premise and SAP
- #22: Production should be most loved place to be
- #24: Isolated team Focus on manual testing via click procedures Different degrees of test automation, but always linked to high effort
- #26: Past Isolated - No Connection to Development Responsible to keep stuff running No/Low focus on automation and self-service Be aware: Operating a cloud solution will be no fun at the beginning