Cloud migration can arise many questions – Which applications to move? Which private or public clouds to use? Which application in which cloud? What security norms to take after? What all things should I be cautious about?
There is a touch of research and learning required in discovering answers to the above inquiries. Be that as it may, here are 10 points you will have to break down while choosing your cloud migration strategy.
1. Change in rationality – “Design not to fail – Design for failure”. In conventional approach you plan your deployment design such that it should not leads to failure (at any cost – it takes a ton of cost). Be that as it may, in the new cloud best practices, recommends you to be prepared for failure, which is an entirely unexpected (yet strong) approach.
2. Application Migration approach – there are numerous degrees of changes you might need to do to your application relying upon your here and now and long haul technical/technical objectives.
- Virtualization – This model encourages a quick and simple migration to cloud as no progressions will be required to the application. For legacy applications, ideal candidate is required.
- Application Migration – For this situation your application will experience design changes and minimal architecture changes, so as to make it ideal for a cloud model of deployment. For instance, you may utilize a No SQL database available on cloud.
- Application Refactoring – This model will require a noteworthy update of your application appropriate from the architecture point of view. This is normally done when you need to use the most recent technology stack.
3. Information management – Plan for appropriate backup strategy and archival for your information. As a best practice, keep the static information close to the user and dynamic information close to compute. This should be possible by utilizing CDN techniques and caching individually.
4. Re-platforming – Expect to have platform similarity issues when you are changing from one stage onto the next (ex: Unix to Linux, Windows 2003 to Windows 2008)
5. Integration – If you are planning to hold a portion of the applications in-house (or in nearby datacenter), then you might need to take a look at the performance / integration perspectives. This while, the applications are gathered and henceforth, data transfer is simple. However, now as the cloud migration application should talk over internet to the applications sitting inhouse. This could lead to bandwidth and performance related issues.
6. Licensing – Confirm if the present set of software/tools you are utilizing, support a cloud based Licensing model. Especially on the off chance, that you are wanting to utilise the elasticity of cloud computing, to ensure that your licenses are going well with such a setup.
7. Security – Review your application’s security. Since every one of your information is put away in the cloud you might need to guarantee that every one of the layers embrace the encryption best practice to guarantee that information is not readable, notwithstanding when it falls in the wrong hands. Consider utilizing security keys issued by an alternate source than the one you are utilizing for deployment.
8. Automation – Look for automation however much as could be expected. Cloud Automation helps in enhancing your efficiency as well as eliminates possibility of human error.
9. Communication – Choose your network configuration in light of the internal/external communication prerequisites of your applications. Abstain from utilizing internet for internal communication between applications as this won’t just expand your cost but also additionally builds the security danger.
10. Vendor lock-in – Keep an eye out for the vendor lock-in angle. While you can basically avoid using the cloud vendor benefits that may not be the powerful solution for your application. You have to weigh the advantages and disadvantages of which services you need to utilize and to what extent you need to utilize.