Migrating to Cloud Best Practices and Strategies Srinivasa Raghavan, CTO Office
Business Drivers for Cloud Agility Cost New Capabilities 2
Cloud is not a single technology 3
Many variations possible Public Cloud Private Cloud Hybrid Cloud SaaS PaaS IaaS 3 rd party Hosting Multiple vendor products will be typically needed for implementing each choice Corporate Data Center 4
Dimensions to consider Dimension Service Model Delivery Model Type of enterprise Internal or external stakeholders Use Cases Technology Choices 1. Benefits versus risks for each implementation choice 2. Each choice will have its own set of best practices 5
This session will not talk about any specific Cloud platform or technology More from <<SI, enterprise, application>> perspective Methodology should be similar 6
Sub questions Hence one could ask sub-questions such as How do I migrate to public Cloud? How do I migrate my applications to AWS? How do I migrate my applications to XYZ? How do I migrate from my current e-mail system to Gmail? How do I migrate to a private Cloud? And so on 7
First do the Strategy 1. Business drivers, inventory 2. Identify the use cases, service and deployment models 3. Identify technology stack 4. Check application suitability and re-engineering requirements 5. Compute the ROI 6. Impact on related processes SDLC, security, billing and settlement, 8
Typical Cycle Plan Design Migrate Manage 9
Planning Plan Design Migrate Manage 1. Understand the requirements, revalidate choices made 2. Identify groups based on dependencies a) Communication Patterns b) Deployment dependencies same server, etc. c) Try to make the set as self-contained as possible 3. Define critical-to-quality parameters for migration success Data loss, performance, security, corporate policies, etc. 4. Migration time window and constraints 5. Co-existence and fallback options 6. Benchmark existing applications for better comparison during UAT 7. Run-on-the-Cloud versus exploit-the-cloud 8. What are the Systems impacted due to this migration and their integration requirements 9. Signoff from customers 10
Design Plan Design Migrate Manage 1. Understand the capabilities and limitations of each Cloud product to be used 2. How should the application be re-architected for the above? 3. Data migration 4. Integration 5. Non-functional requirements 6. Capacity Planning 7. Changes to upstream or downstream systems 8. What toolsets are available for automation 9. Deployment Setup firewall configurations, network, 10.Signoff from customers 11
Exploit-the-Cloud Leverage the Cloud for Performance, Scalability, High-availability, A true Cloud application uses one or more of these features - Horizontal Scalability Multiple Regions provided No-SQL versus RDBMS (based on CAP Theorem) File versus blob storage VM Image as a configurable item Auto-scaling Load balancing Automated Provisioning Needless to say, IaaS (and PaaS) offer most flexibility in implementing the above 12
Migrate Plan Design Migrate Manage Do a pilot migration first For Mitigating Risks End-User Involvement is critical (especially for SaaS) Phased and parallel Migration Based on application groups identified You could look at within application group too For example, Hybrid model Decommission the legacy system 13
Manage Plan Design Migrate Manage User Training Managed Services 14
Some examples SaaS PaaS IaaS Legacy mailbox migration Archives User Training Corporate Policies on E- mail Co-existence E-mail relaying Integration Security Capacity Planning Decommissioning Test Environments Baseline code Upgrade to latest version of software Abstract the Cloud dependencies Loosely coupled (queues) Horizontal scalability best practices Thoroughly test the deployment Move dependent applications together Cloud Management Exploit-the-Cloud: When to use what feature 15
Summary Many options are possible when one speaks of Cloud Planning is key Migration approach not much different to conventional migration approaches The toolset and the specifics will depend on Service Models, Deployment Models, and vendor product capabilities Exploit-the-cloud could lead to some additional effort 16
Thank You 17