Book Image

Hybrid Cloud for Architects

By : Alok Shrivastwa
Book Image

Hybrid Cloud for Architects

By: Alok Shrivastwa

Overview of this book

Hybrid cloud is currently the buzz word in the cloud world. Organizations are planning to adopt hybrid cloud strategy due to its advantages such as untested workloads, cloud-bursting, cloud service brokering and so on. This book will help you understand the dynamics, design principles, and deployment strategies of a Hybrid Cloud. You will start by understanding the concepts of hybrid cloud and the problems it solves as compared to a stand-alone public and private cloud. You will be delving into the different architecture and design of hybrid cloud. The book will then cover advanced concepts such as building a deployment pipeline, containerization strategy, and data storage mechanism. Next up, you will be able to deploy an external CMP to run a Hybrid cloud and integrate it with your OpenStack and AWS environments. You will also understand the strategy for designing a Hybrid Cloud using containerization and work with pre-built solutions like vCloud Air, VMware for AWS, and Azure Stack. Finally, the book will cover security and monitoring related best practices that will help you secure your cloud infrastructure. By the end of the book, you will be in a position to build a hybrid cloud strategy for your organization.
Table of Contents (19 chapters)
Title Page
Copyright and Credits
Software Hardware List
Packt Upsell
Contributors
Preface
Index

Use cases of a hybrid cloud 


We can categorize the use cases broadly into three, based on the existence of different tiers of applications in the clouds, and also the different applications in an enterprise: 

  • Isolated use cases 
  • Distributed use cases
  • Coexisting use cases 
  • Supporting application use cases 

Isolated use case 

This is one of the simplest use cases. In this, an enterprise runs some applications in a public cloud and others in a private cloud, the applications don't communicate among themselves regularly, but may transfer data using a batch process. 

It might also be the case that one application uses the services of the other - with the communication over an API. 

A good use case in this category would be development in public/production on a private cloud (or vice versa). 

In the following diagram, the left side is the public cloud and the right side is the private cloud. The applications running on both sides are isolated - which means a nominal delay in the communication path is acceptable...