As Cloud Computing rapidly evolves, newer deployment strategies such as Hybrid-Cloud, Multi-Cloud and On-Prem Cloud are emerging. More and more enterprise solution providers are offering support for a combination of these deployment targets. It is imperative that the larger organizations have a clear Hybrid-Cloud and Multi-Cloud strategy to avoid cloud lock-in and to de-risk business decisions. What do each of these terminologies mean? What is the scope of each and overlap if any? We will discuss the emerging best-practices across these interdisciplinary trends, especially in the context of Modern Data and Analytics Platforms and Enterprise Self-Service.

1. Chai Atreya, Director of Engineering, Teradata
Emerging Practices in On-Prem Cloud,
Hybrid-Cloud & Multi-Cloud Strategies

2. Chai Atreya
Director of Engineering
Teradata
Analytical Ecosystem and Cloud Engineering

3. 3
Agenda
• Significance
• Terminology
• Trends
• Architecture
• Challenges

4. 4
Significance

5. 5
Data Architecture has changed

6. 6
Why care?
Hybrid-Cloud and Multi-Cloud are the eventual state that most
businesses will operate in.
Forrester says:
“99% of cloud decision makers believe there are benefits to
using consistent, hybrid cloud platforms, services and tools.”
According to a new market research report published by
MarketsandMarkets™, the global market size for hybrid cloud is
expected to grow from USD 44.60 billion in 2018 to USD 97.64
billion by 2023.

7. 7

8. 8

9. 9
Demand will only increase

10. 10
Terminology

11. 11
Terminology
• Hybrid Cloud
“(Hybrid) 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)“
- National Institutes for Standards in Technology (NIST)
• On-prem or Private Cloud
“(Private) 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. “
- National Institutes for Standards in Technology (NIST)

12. 12
Terminology
• Multi Cloud
Multi-cloud is a strategy where an organization leverages two or more
cloud computing platforms, often to meet specific workload needs, but
not connected or orchestrated between them.
A Hybrid-cloud is not a Multi-cloud, though a
Multi-cloud may include hybridization.

13. 13
Comparison
Source: Placeholder

14. 14
Trends

15. 15
Amazon vs Microsoft vs Google
• Amazon
• Initially reticent
• Recent years
• Storage Gateway
• AWS Direct Connect
• AWS CodeDeploy
• Hybrid cloud partnership
with VMWare
• Amazon EKS
• Microsoft
• Most vocal as hybrid cloud
• Azure Stack
• AKS (Azure Kubernetes Service)
• Google
• VMware CEO Diane Greene
• Embraced hybrid cloud
• Partnership with Nutanix and
VMWare
• Created Kubernetes
• GKE (Google Kubernetes
Engine)

16. 16
Why Hybrid or Multi-cloud?
• Data Sovereignty
• Data Autonomy or Portability
• Best of Breed Services
• Avoid Vendor Lock-in
• Security and Privacy
• Balancing flexibility and regulation
• Multi-year 100% uptime
Ultimately “De-risking Business Decisions”

17. 17
Data & Analytics Use-cases
• Cloud Bursting
• Load and resource balancing to manage peak periods
• Cloud Data Lab (Untested Workloads)
• Allowing greater end user self-service and exploration
• Cloud Disaster Recovery & HA
• Providing lower-cost, off-premises environments for
disaster recovery
• Cloud Services Brokering
• IT Operations abstracting deployment to public, private
or virtual environments.
• Regulatory requirements
• Data sovereignty, security regulations

18. 18
Architecture

19. 19
Containers & Kubernetes
• Containers
• Offer cloud portability
• Accelerated Multi-cloud and Hybrid-cloud adoption
• Kubernetes
• Control Plane for Cloud Portability
• Move containerized applications between clouds
without disruption
• Kubernetes Multi-cluster federation
• Kubernetes building to federate clusters running in
different cloud providers
• Easy migration of workloads

20. 20
Google Architecture guidance
Google offers the following guidance to achieve a
heterogeneous Kubernetes environment:
• Expose Kubernetes services to enable traffic direction among
multiple cluster implementations using the domain name
system.
• Consider the use of service mesh, such as Istio or Linkerd, to
facilitate cross-cluster, multi-cloud service discovery.
• Use private, low-latency networks between clusters for shared
services, such as databases.

21. 21
Google Cloud CTO
• More than 50% of GCP customers also use other public clouds
(multi-cloud). – Brian Stevens, Google Cloud CTO
• Google Cloud Services Platform (CSP)
• a hybrid cloud offering
• Vendor’s managed Kubernetes service and
• Open source Istio service mesh.
• Service mesh
• Enterprise can secure and build distributed networks
• Extending from On-prem to Cloud

22. 22
CNCF
Cloud Native Computing Foundation
• “CNCF is an open source software foundation dedicated to making cloud native
computing universal and sustainable. Cloud native computing uses an open
source software stack to deploy applications as microservices, packaging each
part into its own container, and dynamically orchestrating those containers to
optimize resource utilization.”
CNCF Hybrid Cloud Architecture Ecosystem:
• Containerd – container runtime
• CNI - Container Networking Interface
• Envoy – service mesh, by Lyft
• Linkerd – cloud native mesh, by Twitter

23. 23
Source: Placeholder

24. 24
Multi-Cloud Providers
• Spinnaker - Open source, multi-cloud continuous delivery
platform, from Netflix
• Platform9 Systems - manages hybrid cloud infrastructure with
SaaS managed Kubernetes cloud solutions.
• StackPointCloud - create, and manage Kubernetes clusters
on cloud provider of your choice
• Upbound.io - Manage disparate cloud environments as one
• More
RightScale | ZeroStack | AppOrbit | AtScale | HashiCorp

25. 25
Challenges

26. 26
Challenges
• Costs can multiply in a multi-cloud world.
• Different interfaces for infrastructure and configuration and
developer experience.
• Vendor maturity variance with Multi-cloud and Hybrid-cloud.
• Network segmentation and extension.
• Security identities, RBAC, audit and compliance.

27. 27
Takeaways

28. 28
Remember from this talk
• Hybrid Cloud and Multi Cloud are Real – and they are becoming the
New Norm.
• You cannot buy a “Point Solution” for Hybrid Cloud.
• CNCF and Open source are going to play a key role in the evolution.
• Expect your vendors and solution providers to have a clear Hybrid
Cloud strategy.
• Prioritize Hybrid Cloud Platforms with Strong Automation, Security and
Interface consistency.