liveBook · Manning

Hybrid deployment

As explained in Think Like a CTO

A cloud environment that combines private-cloud and public-cloud resources and allows workloads or capacity to span them.

A hybrid deployment combines private- and public-cloud resources. It can suit an organization with substantial existing hardware: a private cloud keeps that investment useful, while public-cloud resources can augment it when private capacity runs out. section 8.3.1

When private capacity runs out

If the private cloud has no resources left for additional demand, the public cloud can cover the shortfall transparently. The organization still needs people to manage its private-cloud pool and hardware. section 8.3.1

Before choosing this approach, ask:

  • Can we staff and manage the private-cloud pool despite the remaining hardware overhead? section 8.3.1
  • Have we designed and tested security, and planned and practiced for failures? section 8.3.1

How Think Like a CTO covers it

How deep it goes
Defines the private–public combination and capacity augmentation, but does not provide deployment steps.
Examples
Illustrates public-cloud resources transparently covering a shortfall when private-cloud capacity is exhausted.
What it assumes
Builds on familiarity with traditional hardware installations while explaining the operational roles of private and hybrid clouds.
What you can do after
Evaluate/understand whether existing hardware, management resources, and capacity needs make a hybrid approach appropriate.
How it connects
Links private cloud, public cloud, hardware provisioning, security, and failure planning.

Also explained in

Compare how 7 books explain hybrid deployment →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.