Planning for Deployment

The hybrid cloud isn’t a single architectural model; rather, it’s a combination of a lot of different services that are located on different platforms. Therefore, there isn’t a simple way to define a hybrid architecture. Instead, from an architecture perspective, it’s important to look at the relationship among the services that are used together. Therefore, the usage of cloud management technologies (see Chapter 4 for more details on hybrid cloud management) needs to be considered as part of the architectural framework of the hybrid cloud.

In the hybrid cloud, you will never bring all services and elements together as though they were one system. Instead, you need to have a clear understanding of the distributed services and how they relate to each other. Many of the approaches require the creation of best-practices templates that can be used to create the right linkages between services. One of the best practices needed is to be able to keep track of what task a specific service executes, the rules for how it can be used, as well as definitions and dependencies. But the issues don’t stop with dependency. In a world where you’re going to leverage services based on different physical and virtual environments, you need to think about how the entire environment behaves under different circumstances. A well- designed hybrid cloud environment has to be built to support change. Change can be the addition of an additional cloud service, such as a SaaS application ...

Get Hybrid Cloud For Dummies now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.