Research: This is the first step in transforming on-premise business software into a cloud environment. Our Cloud computing Experts will go through existing Applications & Data systems to conduct an in-depth research on evaluating the best suitable cloud model(Public/Private/Hybrid). We will ask a lotof questions inthis phase
Depending on several factors like integrations, interdependencies & management tasks a cloud computing model(public, private or hybrid model) of cloud computing is derived
A report on the finding will be submitted Analysis: A professional Analysis on the resources available and the required resources to successfully transform the most immediate workloads is conducted. An Analysis report is submitted, This report will also include an analysis on the cloud transformation requirements including OS capabilities, bandwidth requirements, storage, virtualization, ports and technical manpower requirements for a successful cloud transformation Evaluation: This stage will gather specific data and information regarding several readily available vendor offerings in the market and also prepare the most suitable mapping of the requirements to readily available vendor offerings. Sevate has partnerships with several Vendors offering cloud computing services and will perform a unbiased 3’r party evaluation of the most suitable model being offered in the markets
Plan: Migrating legacy enterprise data and applications into a cloud environment is suely not a small task.
It is absolutely mandatory to ensure that all stakeholders within/outside the organization are on the same page.
Cloud migrations typically require in-depth planning that covers costs, tools, security, governance and skills, amongst other considerations.
For a successful cloud migration strategy, we have a detailed checklist of tasks Approach: The Approach stage identifies Standards including HTTP, HTML, DHTML, XMPP, SSL, and OpenID
Web services such as REST, SOAP, and JSON Service providers including Google, Microsoft, Amazon, Yahoo, IBM, EMC/VMware, Salesforce.com, and others Hardware, infrastructure, clients, platforms, applications, services, and storage Platform as a Service (PaaS), Software as a Service (SaaS), and Software plus Services (S+S) Custom application development environments, frameworks, strategies, and solutions Local clouds, thin clients, and virtualization Costs, benefits, security issues, regulatory concerns, and limitations Migration, best practices, and emerging standards Discover: Discovery stage determines * What’s in the environment * What are the interdependencies * What’s going to be easy to migrate * What’s going to be hard to migrate * How to migrate each application
Discover whether to
1. Rehost Applications:“lift-and-shift: Rehosting can be automated
2. Replatform Applications:“lift-tinker-and-shift”
3. Repurchase Applications:Move to a different product. Moving to a SaaS platform
4. Refactor / Re-architect Applications:Re-imagining how to add features, scale or performance that would otherwise be difficult to achieve in the application’s existing environment
5. Retire Applications:Get rid of non-useful redundant applications
6. Retain Applications:Usually this means “revisit” or do nothing (for now)
Prioritize: It is essential to employ a staggered approach and prioritize applications to be moved to the cloud in order to mitigate and reduce risks associated with cloud application migration
a) Identify the type of application: It is essential to prioritize the type of application chosen for migration. Is the application is mission critical? Then it should have the lowest priority
b) Are there any legal requirements for co-location of cloud applications/data in a particular place? Does your cloud encompass multiple geographical locations? You may have to consider legal stipulations as well as capabilities of the selected cloud platform
Consider usage patterns: Usage patterns in terms of predictability, unpredictability and consistency should be considered. This will help identify the amount of hardware volatility needed during application migration to the cloud.
A predictable peak is exemplified by most financial applications, which invariably have a specified period during which they perform a bulk of their processing. On the other hand, in the retail sector for instance, promotions or sale cycles may or may not deliver as expected, resulting in unpredictable peaks. Then again, human resource management applications usually have fairly consistent usage. Each application category should thus be measured in terms of usage patterns, to determine hardware and infrastructure requirements prior to application migration.
For instance, if the usage pattern is unpredictable with peak loads causing SLA misses (for example, in retail), such an application should have a higher priority to be moved to the cloud. This will ensure that your organization is would be equipped to handle SLA misses.
Determine if the application needs internal or external user support: Applications that have external users will have lower priority of migration to the cloud than those with internal users. External user support implies exposing the private cloud over the demilitarized zone (DMZ) and to the outside world as well. In such a situation, additional security measures are required in the private cloud. Consider the application architecture and design: Place higher priority to Apps which have a application architecture/design that promotes parallelism of computing operations. SOA based Apps: An SOA-based application has higher priority and has several benefits that make it fit for cloud application migration. Service oriented architecture will generally lean toward having a clearly defined interface and clearly defined encapsulated functionalities, which will be easy to transfer to the private cloud.
Evaluate the application’s statefulness: Stateless applications should have higher priority for migration to the cloud. Stateful applications must be migrated to a more persistent type of storage, wherein the state can be externalized and stored
Dependency on third-party software/components: latency/bandwidth/licensing/compatbility constraints in communicating with third components/services need to be checked before migration Apps to the cloud Sample: This stage involves migrating a few low priority applications into the set cloud environment
Test: This stage involves comprehensive testing of the migrated applications for usability and technical factors
Coordinate: This stage involves Coordinating between Management, Resources, Service providers, Technology & Costs Customize: This stage is based on decisions made in the discover stage regarding application migration
Migrate: This stage involves the actual migration of the application into the cloud environment
Optimize: This stage optimizes the migrated cloud application for security, performance etc
Test: This stage is actually a retest of the application in the cloud environment, any anamolies occurring in the migrated application are documented and resolved
Train: This stage involves training and knowledge transfer of the completed cloud migrated to the users & responsible teams
To discuss the value addition of this service to you
please contact us on Skype @ sevate_ for a No-obligation online meeting