How to move to the cloud

626 views
515 views

Published on

This presentation looks at the practical issues for moving applications to the cloud.

It addresses the need to choose the applications carefully and how to decide which type of cloud platform is suitable for delivering cloud benefits.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
626
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
35
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • This diagram demonstrates how cloud, location, performance and applications can be brought together. General applications such as e-mail and collaboration are not high performance and can be placed on public cloud. At the other end of the spectrum are applications that are business-critical, highly sensitive and require high performance systems, such as ERP, finance and M2M trading. These are best run on dedicated systems where the business can provide security and risk analysis.
  • How to move to the cloud

    1. 1. HOW TOMOVE TO THE CLOUD?Application migrations offer new revenue opportunitiesBy Jelle Frank van der Zwet & Ian Murphy@interxion
    2. 2. INTRODUCTIONThis presentation looks at the practical issues formoving applications to the cloud.It addresses the need to choose the applicationscarefully and how to decide which type of cloudplatform is suitable for delivering cloud benefits.2 How to move to the cloud?
    3. 3. INTRODUCTIONWe want to lay down some straight-forward advice and steps on how thiscan be achieved.That’s what this presentation delivers.3 How to move to the cloud?
    4. 4. INTRODUCTIONThe issues addressed are: WHAT APPLICATIONS GO WHERE? CHOOSING A CLOUD DEPLOYMENT MODEL• IaaS• PaaS• SaaS YOUR MIGRATION TO THE CLOUD• Migration paths to the cloud ASSESSING RETURN ON INVESTMENT (ROI)• Cloud premiums4 How to move to the cloud?
    5. 5. WHAT APPLICATIONSGO WHERE?How to move to the cloud?5
    6. 6. WHAT APPLICATIONS GO WHERE?6 How to move to the cloud?
    7. 7. WHAT APPLICATIONS GO WHERE?Not every application is suitable for cloud deployment.Advising customers on what applications should be deployed in or out ofthe cloud can be complicated.7 How to move to the cloud?
    8. 8. WHAT APPLICATIONS GO WHERE?8 How to move to the cloud?1. Is the application data business-sensitive?2. Where will the data be held:locally, or in the cloud with theapplication?3. Can the location of the data bedetermined to ensure thatcompliance is adhered to?4. Is the application business-critical?5. Does the cloud provider offerbetter disaster recoverycapabilities than you currentlyuse?6. How is data secured?
    9. 9. CHOOSING A CLOUDDEPLOYMENT MODELHow to move to the cloud?9
    10. 10. WHICH DEPLOYMENT MODEL?There are three key deployment models that underpin the right cloud migrationpath to take: Infrastructure as a Service (IaaS)• IaaS is a basic cloud service. It provides resources such as virtualmachines (VM), network load balancers, storage and connectivity.• To take advantage of this model, computing resources such asCPU, memory, storage and network are added to a VM and then anapplication is deployed into that same VM.• While the underlying platform is managed by the cloud provider, the user ofthe platform is responsible for maintaining their applications and takingbackups.10 How to move to the cloud?
    11. 11. WHICH DEPLOYMENT MODEL?Platform as a Service (PaaS)• PaaS is a computing platform, operating systems, databases andapplications delivered by the cloud provider.• Customers deploy onto, and developers write code for, the PaaS. This isoften a highly automated and scalable environment.• Management tools ensure resources are provisioned when demandreaches a given level.11 How to move to the cloud?
    12. 12. WHICH DEPLOYMENT MODEL?Software as a Service (SaaS)• The application software is installed in the cloud and accessed by the useronly when needed.• The cloud owner manages the software and owns the licenses andeffectively rents the software to the users which means they makesignificant savings by only paying for software when they are using it.12 How to move to the cloud?
    13. 13. WHICH DEPLOYMENT MODEL?13 How to move to the cloud?
    14. 14. YOUR MIGRATIONTO THE CLOUDHow to move to the cloud?14
    15. 15. MIGRATION PATHS TO THE CLOUDAccording to Gartner, there are five key migration paths to a fully enabledcloud environment: Re-host on IaaS Re-factor for PaaS Revise for IaaS or PaaS Rebuild on PaaS Replace with SaaSEach of these has their pros and cons and offers opportunity for the systemsintegrator to add value.15 How to move to the cloud?
    16. 16. PATHS TO THE CLOUD Re-host on Infrastructure as a Service (IaaS)16 How to move to the cloud?Pros Cons• Speed: Applications can be easily movedfrom physical to virtual using a variety of toolsand the application can then be uploadeddirectly to the cloud provider’s environment• Cost savings: No local hardware to buy andno power or cooling costs• Scalability: Customer is responsible for addingor removing resources which can lead to a delayin incident response• Maintenance: Customer is still responsible forthe maintenance and patching of their virtualmachines• Distributed applications: These require carefulchecking to ensure that all relevant elements ofthe application have been captured in the virtualmachine otherwise the applications will fail• Backups: If data is uploaded, there must be off-site backups by the customer
    17. 17. PATHS TO THE CLOUD Re-factor for Platform as a Service (PaaS)17 How to move to the cloud?Pros Cons• Familiarity: Developers are using the samelanguages and tools that they currently use• Integrated management: Operations teamsare using a single management tool tomanage local and cloud based systems• Savings: No need for retraining the ITdepartment to learn new management tools orlanguagesLock-in: There is a risk of lock-in when thedeveloper embeds access to other services fromthe cloud provider. This can be avoided bysticking to the capabilities of the genericlanguages and frameworks.• Missing capabilities: Only those featuressupported by the cloud provider will be availablein the development and support frameworks. Thismay mean that early in the cloud provider’sdeployment, there could be limitations on whatcan be achieved.
    18. 18. PATHS TO THE CLOUD Revise for IaaS or PaaS18 How to move to the cloud?Pros Cons• Performance: Application extensions that arewritten to perform natively on the cloudplatform will run faster and take advantage offeatures that may not be available on theexisting platform.• Faster time to market: Writing new front-endsto legacy applications means delivering quickwins to Business Units.• Integration: Highly integrated applications willmake it easier for business units to takeadvantage of IT systems and the data theycontain.• Slower time to market: If the entireapplication is to be moved to the cloud andthen extended to take advantage of newservices, this is likely to take quite some timebefore benefits are available.
    19. 19. PATHS TO THE CLOUD Rebuild on PaaS19 How to move to the cloud?Pros Cons• Performance: Applications that are written toperform natively on the cloud platform will runfaster and take advantage of features that maynot be available on the existing platform.• Savings: Moving from large legacy hardwareestates that are often expensive to maintain andrun will result in significant cost savings.• New platform features: Taking advantage of thenew features inside the cloud provider’s platformwill save the IT department having to add those toexisting applications. As a result, this shouldgenerate a higher ROI than the Revise option.• Lock-in: Once applications have been tightlyintegrated with the service provider’s platform, itmay be difficult to move from that platform to analternative supplier.
    20. 20. PATHS TO THE CLOUD Replace with Software as a Service (SaaS)20 How to move to the cloud?Pros Cons• Cost savings: No local hardware, nosoftware licences and no power or coolingcosts. This is virtually the same as anoutsourced solution with the benefit of flexibleresource allocation for workload flows.• Access to high value enterprise softwarecomes within the reach of SMEs who can nowafford to deploy software that can offer acompetitive advantage.• Scalability: This is handled automatically bythe cloud provider through their SaaSplatform.• Lock in: For commodity software such as office-based applications this is not an issue, but wherethe software needs significant customisation, anybreakdown in the business relationship betweenthe business and the cloud provider could be aproblem.
    21. 21. ASSESSINGRETURN ON INVESTMENTHow to move to the cloud?21
    22. 22. ASSESSING ROI• The real ROI for cloud is about the costs that it would take to deliver thesame level of service internally.• This includes hard and soft metrics such as uptime, user experience, costof hardware / software, integration, cost of bandwidth, data centre powerand cooling costs, and staff costs22 How to move to the cloud?
    23. 23. ASSESSING ROI Cloud Premiums• The key to establishing an ROI on cloud is to look at what a cloud solutionenables that could not have been achieved using existing IT systems orplatforms. This should be thought of as a cloud premium• The most effective way of determining the cloud premium as part of theROI is to compare the business case with what cloud offers.• When doing this, consider what it would cost to deliver this using existing ITinfrastructures and tools. This will help clarify what is cloud premium andwhat is simply a benefit from more flexible processes.23 How to move to the cloud?
    24. 24. ASSESSING ROI24 How to move to the cloud?Business Case Cloud PremiumReducing the cost ofdevelopment and testingenvironments• The speed with which a testing environment can beprovisioned• Ability to do more intensive and extensive testing ofapplications• Access to high value test tools on demand via SaaS• Access to test professionals in different locationsScalability • Ease of adding additional compute, network and/or storageresources• Ability to shrink resource pool when not requiredCompetitive advantage • Faster time-to-market for new applications and solutionsmeans new market opportunities can be quickly explored• Speed of identification of trends and designing competitivesolutions• Lower cost of IT releasing more money for other parts of thebusiness
    25. 25. TO DOWNLOAD THEWHITE PAPER IN FULLCLICK HERE

    ×