Download to read offline
Uploaded byConSol Consulting & Solutions Software GmbH
Cloud-Migrations
The document discusses different strategies for migrating applications to the cloud. It outlines six common migration strategies: 1) Rehosting which is lifting applications as-is to the cloud with minimal changes, 2) Replatforming which involves minor changes to applications to optimize them for the cloud, 3) Repurchasing which means migrating to cloud-based software-as-a-service applications, 4) Refactoring/re-architecting which involves redesigning applications to take advantage of cloud-native features, 5) Retiring applications that are no longer needed, and 6) Retaining applications without changes if migration is low priority. It advises starting with quick wins that have few dependencies and conducting a cloud readiness
More Related Content
More from ConSol Consulting & Solutions Software GmbH
Cloud-Migrations
- 1. Migrationsstrategien: Cloud ist nichtgleich Cloud Lukas Höfer Cloud Solutions Architect 22.10.2019
- 2. Cloud Migration StrategiesSlide 2 Agenda
- 3. Cloud Migration StrategiesSlide 3 Agenda What is Cloud? Where to migrate to? Which migration strategies exist? Where to start? Are you ready?
- 4. Cloud Migration StrategiesSlide 4 Why Cloud Migration? Cost - Productivity - Availability- Flexibility
- 5. Cloud Migration StrategiesSlide 5 There is no Cloud
- 6. Cloud Migration StrategiesSlide 6 Cloud Models Private Public
- 7. Cloud Migration StrategiesSlide 7 Cloud Models Private Public Hybrid
- 8. Cloud Migration StrategiesSlide 8 Cloud Models Private Public
- 9. Cloud Migration StrategiesSlide 9 Cloud Models Private Public
- 10. Cloud Migration StrategiesSlide 10 Cloud Models Private Public
- 11. Cloud Migration StrategiesSlide 11 Shared Responsibility Model Private Customer Service Provider Networking Storage Serves O/S Virtualization Middleware Runtime Data Application On-Premise Networking Storage Servers O/S Virtualization Middleware Runtime Data Application IaaS Networking Storage Serves O/S Virtualization Middleware Runtime Data Application PaaS Networking Storage Servers O/S Virtualization Middleware Runtime Data Application SaaS
- 12. Cloud Migration StrategiesSlide 12
- 13. Cloud Migration StrategiesSlide 13 The Six R‘s of Cloud Application Migration Rehosting Replatforming Repurchasing Refactoring / Re-architecting Retire Retain
- 14. Cloud Migration StrategiesSlide 14 1 Rehosting aka lift-and-shift. Move the application as-is to the Cloud (IaaS) • Fast and mostly simple • No refactoring needed • Enables vertical scaling
- 15. Cloud Migration StrategiesSlide 15 2 Replatforming Move the application with minor changes to the Cloud (IaaS/PaaS) • Still quite fast and mostly simple • Improve performance/safe costs • Enables vertical scaling
- 16. Cloud Migration StrategiesSlide 16 3 Repurchasing Move to a different application or license in the Cloud (SaaS) • Fast and simple • Using the advantages of SaaS
- 17. Cloud Migration StrategiesSlide 17 4 Refactoring / Re-architecting Redesign parts of the application to enable Cloud Native features (PaaS) • Move to service oriented architectures • Most expensive option • Truly leverages the advantages of the Cloud
- 18. Cloud Migration StrategiesSlide 18 5 Retire Get rid of applications • Discover your portfolio • Turn of unused applications • Safe money
- 19. Cloud Migration StrategiesSlide 19 6 Retain Do nothing • Discover your portfolio • Low priority to migrate • Wait for deprecation
- 20. Cloud Migration StrategiesSlide 20 The Six R‘s of Cloud Application Migration https://aws.amazon.com/de/blogs/enterprise-strategy/6-strategies-for-migrating-applications-to-the-cloud/
- 21. Cloud Migration StrategiesSlide 21 Where to start? Identify quick wins within your IT Landscape • Few dependencies • Limited userbase • Not business critical • Well documented • Reusable pattern • Keep Compliance and Security in mind!
- 22. Cloud Migration StrategiesSlide 22 Are You Ready? Determine your Cloud Readiness • Are the necessary skills available? • Are all the right people on board? • Are the basic communication paths and responsibilities defined? • Is there central commitment?
- 23. Cloud Migration StrategiesSlide 23 Further Reading https://www.consol.de/unternehmen/downloads/
- 24.
Editor's Notes
- #3 Die cloud scheint etwas zu sein, das nicht ganz fassbar ist. Man sieht es erstmal und es schaut ganz gut und einfach aus, aber um so mehr man danach greift um so diffuser wird das ganze thema. Und genau das macht es schwer über das thema zu diskutieren.
- #4 Die cloud scheint etwas zu sein, das nicht ganz fassbar ist. Man sieht es erstmal und es schaut ganz gut und einfach aus, aber um so mehr man danach greift um so diffuser wird das ganze thema. Und genau das macht es schwer über das thema zu diskutieren.
- #5 Aber warum möchten eigentlich gerade so viele in die cloud migrieren? Kosten – lassen sich prinzipiell senken, da nur das bestellt werden muss, was man tatsächlich benötigt Mitarbeiterproduktivität – wartezeiten durch lange bestellprozesse verschwinden; stichwort self service Ausfallsicherheit des Betriebs – experten am werk; skalierbarkeit, weltweit… serverless Geschäftliche Flexibilität – und freiheit … prinzipiell erstmal kein langer lockin, keine upfront kosten, dynamisch skalierbar….
- #6 There is no cloud, it‘s just someone elses computer
- #13 Jetzt sind die geheimnisse der cloud buzzwords soweit entschlüsselt. Gibt es bis hier hin irgendwelche fragen?
- #14 Rehosting — Otherwise known as “lift-and-shift.” Replattforming — I sometimes call this “lift-tinker-and-shift.” Repurchasing — Moving to a different product. Refactoring / Re-architecting Retire — Get rid of. Retain — Usually this means “revisit” or do nothing (for now
- #15 Rehosting — Otherwise known as “lift-and-shift.” Replattforming — I sometimes call this “lift-tinker-and-shift.” Repurchasing — Moving to a different product. Refactoring / Re-architecting Retire — Get rid of. Retain — Usually this means “revisit” or do nothing (for now
- #16 Rehosting — Otherwise known as “lift-and-shift.” Replattforming — I sometimes call this “lift-tinker-and-shift.” Repurchasing — Moving to a different product. Refactoring / Re-architecting Retire — Get rid of. Retain — Usually this means “revisit” or do nothing (for now
- #17 Rehosting — Otherwise known as “lift-and-shift.” Replattforming — I sometimes call this “lift-tinker-and-shift.” Repurchasing — Moving to a different product. Refactoring / Re-architecting Retire — Get rid of. Retain — Usually this means “revisit” or do nothing (for now
- #18 Rehosting — Otherwise known as “lift-and-shift.” Replattforming — I sometimes call this “lift-tinker-and-shift.” Repurchasing — Moving to a different product. Refactoring / Re-architecting Retire — Get rid of. Retain — Usually this means “revisit” or do nothing (for now
- #19 Rehosting — Otherwise known as “lift-and-shift.” Replattforming — I sometimes call this “lift-tinker-and-shift.” Repurchasing — Moving to a different product. Refactoring / Re-architecting Retire — Get rid of. Retain — Usually this means “revisit” or do nothing (for now
- #20 Rehosting — Otherwise known as “lift-and-shift.” Replattforming — I sometimes call this “lift-tinker-and-shift.” Repurchasing — Moving to a different product. Refactoring / Re-architecting Retire — Get rid of. Retain — Usually this means “revisit” or do nothing (for now
- #21 Rehosting — Otherwise known as “lift-and-shift.” Replattforming — I sometimes call this “lift-tinker-and-shift.” Repurchasing — Moving to a different product. Refactoring / Re-architecting Retire — Get rid of. Retain — Usually this means “revisit” or do nothing (for now
- #22 Rehosting — Otherwise known as “lift-and-shift.” Replattforming — I sometimes call this “lift-tinker-and-shift.” Repurchasing — Moving to a different product. Refactoring / Re-architecting Retire — Get rid of. Retain — Usually this means “revisit” or do nothing (for now
- #23 Technical Team · Infrastructure Engineers, who understand the existing IP addresses, boundary security (firewalls), routing, server build standards, and a whole host of things in between. · Security Engineers, who will ensure that everything is built and coded to meet your company’s security objectives. · Application Engineers, who will ensure that the coding logic of the product you’re building gets built. · Operations Engineers, who will ensure that your ITIL elements can be adapted to benefit from the cloud. · A Lead Architect Business Team: CIO or Direct Report with Single Threaded Ownership Procurement or Vendor Management Legal Lead Chief Information Security Officer Chief Financial Officer or Direct Report Head of Infrastructure Head of Delivery Engineering or Product Manager of the first Cloud Engineering Team Risk Leader (needed in most organizations, but especially regulated ones) Audit Leader (needed in most organizations, but especially regulated ones)