Cloud computing and migration strategies to cloud

1. CLOUD COMPUTING AND
MIGRATION STRATEGIES TO
CLOUD
SOURABH SAXENA
CLOUD CONSULTANT

2. According to Gartner report
The worldwide public cloud services market is projected to grow 17.3 percent in
2019 to total $206.2 billion, up from $175.8 billion in 2018, according to Gartner, Inc.
In 2018, Gartner forecasts that the market will grow 21 percent, up from $145.3
billion in 2017.
The fastest-growing segment of the market is cloud system infrastructure services
(infrastructure as a service or IaaS), which is forecast to grow 27.6 percent in 2019 to
reach $39.5 billion, up from $31 billion in 2018 .
By 2022, Gartner expects that 90 percent of organizations purchasing public cloud
IaaS will do so from an integrated IaaS and platform as a service (PaaS) provider, and
will use both the IaaS and PaaS capabilities from that provider.

3. Cloud computing
Cloud computing has been defined by NIST [2] as a model for enabling
ubiquitous, convenient, on-demand network access to a shared pool of
configurable computing resources (e.g., networks, servers, storage,
applications and services) that can be rapidly provisioned and released with
minimal management effort or service provider interaction.

4. Deployment Models
The National Institutes of Standards and Technology (NIST) publication The NIST
Definition of Cloud Computing, defines four different deployment models for cloud
implementations.
Model Description
Private Cloud The cloud infrastructure is provisioned for exclusive use by a single organization comprising multiple consumers (e.g.,
business units). It may be owned, managed, and operated by the organization, a third party, or some combination of them,
and it may exist on or off premises.
Community Cloud The cloud infrastructure is provisioned for exclusive use by a specific community of consumers from organizations that have
shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be owned, managed,
and operated by one or more of the organizations in the community, a third party, or some combination of them, and it
may exist on or off premises.
Public Cloud The cloud infrastructure is provisioned for open use by the general public. It may be owned, managed, and operated by a
business, academic, or government organization, or some combination of them. It exists on the premises of the cloud
provider.
Hybrid Cloud The cloud infrastructure is a composition of two or more distinct cloud infrastructures (private, community, or public) that
remain unique entities, but are bound together by standardized or proprietary technology that enables data and application
portability (e.g., cloud bursting for load balancing between clouds).

5. Service delivery models
Infrastructure as a Service (IaaS)
IaaS delivers computing infrastructure as a service. Instead of purchasing
hardware and other infrastructure components, customers use some form
virtualization to access outsourced resources. Because consumption is on an
on-demand basis, costs directly reflect the amount of use.
Platform as a Service (PaaS)
PaaS delivers computing and development platforms (for example,
.NET, Java EE, Google applications) as a service, giving users the ability to
deploy and develop applications without significant hardware and software
expense or management time. Since the deployment platform is very
like .NET, there might be limitations of the types of applications that might
supported. For instance, Google App Engine only supports applications
using Python while Heroku supports Ruby on Rails application
Software as a Service (SaaS)
By delivering applications as a service, SaaS offers customers pre-
packaged/pre-built applications through a standard web browser. With
customers can avoid the installation and management of software on their
computers and further benefit from centralized, automatic software
well as lower costs. Customers don’t need to dedicate valuable resources to
software deployment or management.

6. Service Categories
Service Categories Cloud service providers offer varying levels of operational support. They vary in the type
and number of resources managed by the customer versus those managed by the service provider. Table 1
compares the resources that are managed by the customer, agency, or organization against those managed
by the service provider for each service category.
Legend (shading key):
On Premises Infrastructure-as-aService (IaaS) Platform-as-a-Service (PaaS) Software-as-a-Service (SaaS)
Applications Applications Applications Applications
Data Data Data Data
Runtime Runtime Runtime Runtime
Middleware Middleware Middleware Middleware
Operating System Operating System Operating System Operating System
Virtualization Virtualization Virtualization Virtualization
Servers Servers Servers Servers
Storage Storage Storage Storage
Networking Networking Networking Networking
Managed by the Customer/Agency/Organization Managed by the Cloud Service Provider

7. Migrating Applications to the Cloud
Moving your IT infrastructure to the cloud has become a business
necessity for many organizations. However, the profusion of cloud
providers and the process involved in migrating to the cloud can be
intimidating to organizations stuck with legacy applications and an
on-premises setup for their enterprise systems.

8. Reasons for moving workloads to cloud
 Cloud migration allows Dynamic Scalability for business growth a micro and macro
level
 Cloud migration automates all of the software and security updates i.e. Ease of
Management
 Completely automated provisioning, release, and deployment of I.T. resources
facilitate high availability
 Cost transparency and a consumption based pricing model that saves valuable
resources i.e. Cost Savings Complete
 Energy Savings with drastically reduced need for numerous servers, businesses
can save energy and cost
 When Numerous individual’s ether departments, and even companies are able to
share software, applications, and other I.T. resources called as Multi-Tenancy
between
 Real-Time Monitoring Constantly improves performance and provisioning.

9. Issues that may affect our decision while choosing
type of cloud
 Regulatory constraints - If the provider are associated with the any type of health
care or financial industries, there may be privacy or control issues that may affect
use of public cloud here private cloud will be a liable option.
 Security concerns Security is major factor, and the private cloud will be better
option to keep secrecy of the data to be migrated on other hand public cloud
will be proven best when to share resources.
 Performance Public cloud improves performance but at the same time its
negative impacts on some database and application is not negotiable hence it is
necessary to review each application and database performances individually.
Sometimes data is suitable to public as well as private cloud in this case, hybrid
cloud is best solution.

10. Application Migration Strategies: “The 6 R’s”

11. Rehost
 Known as “Lift & Shift”.
 Most rehosting can be automated with tools.
 Though some customers decide to do this manually, they get to know how to apply their legacy systems in the cloud.
 Applications are easier to optimize when they are already running in the cloud
Replatforming
 Also called as “lift-tinker & Shift.”
 Change application platform while preserving existing functionality.
Repurchasing
 This is a move to a SaaS platform.
 Runs outside the infrastructure and is maintained by a third party.
 Eliminates the need for you or your team to spend time on maintenance or updates
 Example: Moving CRM to Salesforce.com, a CMS to Drupal.

12. Refactoring
 Re-imagining how the application is architected and developed, using cloud-native features.
 The drive for this strategy would be to improve scalability, agility, and overall performance.
Retire
 To “Get Rid-off”
 To discover everything in your IT portfolio that are no longer useful and can be eliminated.
 These savings can improve the business, guide your team’s attention and reduce the surface area you have to secure.
Retain
 Also called as “Revist”
 Maybe you’re still riding out some depreciation, aren’t ready to prioritize an application that was recently upgraded or are
otherwise not inclined to migrate some applications.

13. Thanks …..