How can I plan for future cloud readiness?
Started on: 13 August 14
Participants: 3
While we continue to build and deploy new applications within our company and occasionally modernize the existing ones, we are conscious that in the future we may need to move them to the cloud. What are the things we should be doing now to plan for smoothly being able to move them to the cloud in the future?
This challenge is listed under
Cloud Computing
Community
Related Posts:
Initiator
Please login to reply this post
Important:
- We hope the conversations that take place on MyTechLogy.com will be constructive and thought-provoking.
- To ensure the quality of the discussion, our moderators may review/edit the comments for clarity and relevance.
- Comments that are promotional, mean-spirited, or off-topic may be deleted per the moderators' judgment.
3 Suggestions
I am not sure how others plan, but my steps are as follows:
1. Verify that your applications can work well in a distributive environment.
2. Set up services to communicate between systems or processes that will be distributive.
3. For off-the-shelf products, determine if a cloud version exists.
Something else to keep in mind is assessing the value of moving those applications to the cloud. Many companies expect to see immediate returns once they make the move to the cloud. So, understanding the overall impact of a certain application in your environment can help you decide what to move out and what to keep within your own walls.
Two points to consider when architecting for a possible future move to a cloud platform:
1. Plan an architecture that is as open as possible. The technology choices made should offer flexibility and interoperability, so that when the time comes, decisions can be made more easily about how much of the IT stack can be moved to the cloud (e.g., applications, infrastructure, middleware, etc).
2. An alternative view is to insulate the application layer and it’s current environment from the cloud environment by considering the migration as a move to virtualization only. This perspective presents fewer constraints in terms of the future interoperability required.