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

The development cycle and DevOps 


When creating an application, companies follow either a waterfall model or an agile methodology of project management. While there are several changes in how things are done in both of the methods, technically, the steps followed are not that different. 

Each software development cycle technically consists of:

  • Requirement gathering (for bugs or new features)
  • Development/coding
  • Integration of code
  • Testing the code
  • Deployment 

It is a cyclic process and continuously improves the software that is being written. The waterfall and agile have different philosophies of how to perform these steps; the steps themselves don't change. 

For example, the agile development works on the whole cycle in sprints, which are normally two weeks to four weeks long as opposed to a long development cycle in that of a waterfall model. 

Now assume we have to code, integrate, test, and deploy a specific feature within this short time, we will definitely need automation and tooling. Hence,...