This document discusses options for moving workloads to the cloud, including public cloud, private cloud, and hybrid cloud models. It provides details on the characteristics of each model, such as infrastructure ownership and management responsibilities. The document also addresses considerations for organizations in deciding between cloud options, such as regulatory requirements, collaboration needs, and customization requirements. Risks of moving data to the cloud like data loss are presented along with statistics. Overall the document provides an overview of different cloud computing models and factors to evaluate in selecting between them.
11. A recent survey by UBS AG of 101 CIOs in the
U.S. and Europe found that more than half
would move some workloads to a public
cloud, but it would be a gradual process, while
a third of respondents said they were moving
to a public cloud as quickly as possible.
(Wall Street Journal, July 16, 2014)
14. of workers used an unsanctioned cloud service
for document storage in the last 6 months 41%
87%
$1.8
of these workers knew their company had
policies forbidding such practices
(billion) estimated annual cost to remedy
the data loss
New Mobile Survey Reveals 41% of Employees Are Deliberately Leaking Confidential Data http://onforb.es/18h92Nv
15. According to IDC:
• 74% expect their cloud service to
be able to move a cloud offering
back on-premise if needed.
• 63% expect to have a single major
cloud service provider.
• 67% expect to purchase a wide
variety of services from a single
vendor.
• 84% want an established
relationship with a vendor to trust
them as a cloud service provider.
30. Partner Hosted Private
Cloud
• Dedicated environment
• Externally hosted
• Externally or internally
managed
• Internally designed
Self Hosted
Private Cloud
• Dedicated environment
• Internally hosted
• Internally managed
• Internally designed
Shared or Dedicated
Public Cloud
• Shard or dedicated
environment
• Externally hosted
• Externally managed
• Externally designed
Dedicated
Public Cloud
• Partially or fully dedicated
• Externally hosted
• Externally or internally
managed
• Minimal customization
http://social.technet.microsoft.com/wiki/contents/articles/4633.what-is-infrastructure-as-a-service.aspx
Traditional
on premises
31. Private Cloud Hybrid Cloud
Infrastructure
maintained solely
for customer
On premises or off
Managed by the
customer, or by a
3rd party hoster
Multiple
infrastructure
options
Components both
on premises and
off premises
Management
spread between
customer and 3rd
party hosters
Public Cloud
Infrastructure
shared by multiple
customers
Off premises
Managed by 3rd
party on behalf of
customers
32. • Standardized (packaged) platform
• Provided with Service Level Agreements (SLAs)
• Minimal customization
• Both software and hardware infrastructure
provided within the service
33. • Architectural and development access to application services,
storage, and application runtime
• Infrastructure Service Level Agreements (SLAs), but work
must be conducted within agreed framework
• Some customizations allowed, within framework
• Both software and hardware infrastructure
provided within the service
34. • Virtualized hardware and software, including
servers, storage, and network infrastructure
• All components delivered as metered services
(pay per use)
• Complete application control
and customization
35.
36. • Size and geographical distribution of an organization can affect cloud adoption.
• Regulatory compliance and governance requirements can limit cloud options.
• External collaboration may require on prem farms.
• Service-level agreements (SLAs) may limit cloud options.
• Enables customers to use preferred features from SharePoint 2013 on prem and
SharePoint Online.
• It is important to understand the ROI of any proposed solution (and the cost of change).
• Hybrid may be more of a transitional environment from on prem to the cloud.
http://www.sharepointnutsandbolts.com/2014/02/office-365-sharepoint-hybrid-what-you-do-and-do-not-get.html
37.
38. Location / facilities
On Premises Cloud Hybrid
Need space and
maintenance planning Most likely provided
Software licenses
and support
Licensing costs, but
also upgrades and
ongoing support
Included in vendor-hosted
solutions
Hardware and
maintenance
Need to purchase,
support and maintain,
and upgrade as
platform matures
Included in vendor-hosted
solutions
Onsite support,
personnel skills
Administrative,
developer, and end
user skills and training
Still requires
administrative and
possibly dev skills,
end user training
Need space and
maintenance planning
Licensing costs, but
also upgrades and
ongoing support
Need to purchase,
support and maintain,
and upgrade as
platform matures
Administrative,
developer, and end
user skills and training
39. Level of
On Premises Cloud Hybrid
customization Full control
Limited to none in
SaaS, some control
over PaaS, full control
over IaaS
Limited ability to
integrate depending
on SaaS, PaaS, or IaaS
Governance,
auditing, security,
compliance
Many limitations OTB,
but very robust tools
from partners
Limited
Very complex across
on prem and cloud
components, very
manual
Disaster Recovery
and Business
Continuity
Needs to be planned,
limited features OTB
Defined in SLAs
Upgrades and
migration
Some OTB capabilities,
3rd party for tighter
control and
predictability
Microsoft
recommends 3rd
party tools
Very complex across
on prem and cloud
components, very
manual
Some OTB capabilities,
3rd party for tighter
control and
predictability
Discuss E2open background, early forays into cloud infrastructure and what we learned about building SaaS offerings.
Electronic Data Interchange (EDI)
E-commerce
Telecom advances
SOAP and XML
Service-Oriented Architecture
Web Services
Virtualization
Inexpensive hardware
Screen shots of OneDrive, Delve, Groups, Yammer
Talk about how we connect today
Give some examples of team collab
The real risk is not recognizing that your end users are already putting corporate data in the cloud. Use the puppy analogy. Its all about redirect, but in a more secure, controlled way.
You can try it, and if you don’t like it, revert back
The real risk is not recognizing that your end users are already putting corporate data in the cloud. Use the puppy analogy. Its all about redirect, but in a more secure, controlled way.
Decisions need to be made about build or buy, out source or keep in house
Customer receives a completed application and functionality with agreed upon SLAs, system uptime, and quality of service (performance).
The downside is that there is minimal ability to customize, and new features/updates/changes are driven by market demand or the capabilities of the provider.
How do Cloud services differ from traditional managed services?The primary difference is that you say goodbye to the major platform upgrades every 3 or 4 years, and move toward more of an iterative update.
As cloud-based service providers, their revenue model changes dramatically as customers move from a high-cost, project-based model to a recurring revenue model.
An environment that provides great application-level control over the SharePoint environment, including access to cloud storage and other services. However, this greater level of application control shifts support/ownership of the application (SharePoint) to the customer.
Delivered as virtual environments and cloud storage. Customer is responsible for the entire platform and applications. Generally used by ISVs, SIs, and customers with very complex, unique development requirements.
These factors will help you decided how much your own organization can support, as well as help you determine the suitability of vendors