liveBook · Manning

Hybrid cloud

Also called hybrid deployment, hybrid architecture

A hybrid deployment is an architecture that coordinates two or more distinct infrastructure or execution environments within one system.

How 9 Manning books explain it

Kafka for Architects

A hybrid approach combines on-premises infrastructure with cloud-based services in one solution.

How it is used
Supports on-premises operational systems while making selected data available to cloud analytics and other services.
How deep it goes
Explains dual-cluster replication, replicator placement, lag, and cost trade-offs without providing configuration steps.
Examples
Uses a local-to-cloud replication diagram and a Customer 360 operational data store deployment decision.
What you can do after
Evaluate/understand whether dual-cluster replication fits latency, cost, operational, and compliance constraints.

Read how Kafka for Architects explains hybrid cloud →

Think Like a CTO

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

How it is used
Positions hybrid deployment as a capacity strategy for organizations with substantial existing hardware.
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 you can do after
Evaluate/understand whether existing hardware, management resources, and capacity needs make a hybrid approach appropriate.

Read how Think Like a CTO explains hybrid cloud →

Fast by Default

A hybrid architecture combines edge infrastructure for latency-sensitive or lightweight work with origin infrastructure for centralized data access and complex computation.

How it is used
Places latency-sensitive and data-dependent operations across edge and origin infrastructure.
How deep it goes
Explains dependency-based placement, response assembly, and round-trip latency, but stops short of deployment configuration.
Examples
Uses token signing, profile updates, product pages, Vercel measurements, and Netflix Open Connect.
What you can do after
Apply it by analyzing data dependencies, assigning operations to edge or origin, and checking database round-trip costs.

Read how Fast by Default explains hybrid cloud →

Architecting an Apache Iceberg Lakehouse

A hybrid cloud deployment combines infrastructure operated on premises with services or storage provided by public clouds.

How it is used
Connects regulated on-premises data with cloud-native analytics when scaling legacy infrastructure is difficult.
How deep it goes
Explains residency, storage interfaces, federation, and operational tradeoffs but stops short of detailed deployment configurations.
Examples
Uses regulated banking data, EU on-premises storage, cloud analytics, Trino federation, and archival tiering as concrete examples.
What you can do after
Apply it via Trino to query distributed on-premises and cloud data while preserving infrastructure and residency constraints.

Read how Architecting an Apache Iceberg Lakehouse explains hybrid cloud →

Google Anthos in Action

A hybrid cloud deployment operates a platform across a public cloud and one or more on-premises data centers.

How it is used
Deploys and operates a consistent application platform across Google Cloud and on-premises environments.
How deep it goes
Explains placement, connectivity, routing, and migration patterns, but does not detail complete production configuration procedures.
Examples
Uses Anthos across GCP and data centers, Dedicated Interconnect, and traffic splitting between on-premises and cloud services.
What you can do after
Configure and operate platform connectivity, routing, and migration across cloud and on-premises environments.

Read how Google Anthos in Action explains hybrid cloud →

Fundamentals of Cybersecurity

A hybrid cloud combines two or more distinct cloud deployment approaches and supports movement of data and applications between them.

How it is used
Balances public-cloud scalability and flexibility with the control and security of private or community environments.
How deep it goes
Defines a unified combination and gives a workload example, but does not detail technical integration.
Examples
Uses private cloud for sensitive data and public cloud for peak traffic or less-sensitive workloads.
What you can do after
Evaluate deployment choices by balancing workload needs for scalability, control, and security.

Read how Fundamentals of Cybersecurity explains hybrid cloud →

Building Reliable AI Systems

A hybrid deployment architecture combines multiple deployment approaches or environments within one system.

How it is used
Balances model capability, cost, control, and reliability by combining local models with hosted APIs.
How deep it goes
Explains query routing, fallback, and production alternatives to brittle keyword matching without detailing a complete implementation.
Examples
Uses customer-support queries: short factual questions go local, nuanced or risky questions go hosted, and overload triggers fallback.
What you can do after
Operate a routing strategy that directs queries by complexity and shifts traffic or falls back when performance requires it.

Read how Building Reliable AI Systems explains hybrid cloud →

Authorization in Action

A hybrid deployment combines locally running authorization evaluation with remotely managed policy or entity storage.

How it is used
Combines local, low-latency authorization decisions with remotely managed policy and entity storage.
How deep it goes
Describes the local-agent and AVP arrangement, periodic synchronization, and performance and management tradeoffs.
Examples
Uses ACME’s on-premises Customer Collaboration deployments and AWS-hosted SaaS instances as a contrast.
What you can do after
Evaluate deployment tradeoffs between local decision speed and managed policy hosting.

Read how Authorization in Action explains hybrid cloud →

Microsoft Azure in Action

An architecture that combines on-premises infrastructure with Azure resources so workloads and data can operate across both environments.

How it is used
Combines on-premises services with Azure resources when an organization is not ready to move entirely to the cloud.
How deep it goes
Defines the deployment model and works through file synchronization, but stops short of broader hybrid network configuration.
Examples
Uses synchronized on-premises file servers, Azure file shares, File Sync agents, Entra Cloud Sync, and Azure backups.
What you can do after
Apply it via Azure File Sync to synchronize files, support cloud and local access, and reduce additional storage hardware.

Read how Microsoft Azure in Action explains hybrid cloud →

Also covered in

What to know first

Related concepts

Questions about hybrid cloud

What is hybrid cloud?

A hybrid deployment is an architecture that coordinates two or more distinct infrastructure or execution environments within one system.

Which Manning books explain hybrid cloud?

Kafka for Architects, Think Like a CTO, Fast by Default, Architecting an Apache Iceberg Lakehouse, Google Anthos in Action, Fundamentals of Cybersecurity, Building Reliable AI Systems, Authorization in Action and 1 more.

What should I know before learning hybrid cloud?

Manning books that teach hybrid cloud usually introduce self-hosting, caching, cloud provider and infrastructure first.

What is hybrid cloud a kind of?

Hybrid cloud is a kind of deployment model. A deployment model is a specification of how a software system or workload is configured, provisioned, released, hosted, or operated in a target environment.

What are the parts of hybrid cloud?

Hybrid cloud includes private cloud.

What is hybrid cloud also called?

Hybrid cloud is also called hybrid deployment or hybrid architecture.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.