liveBook · Manning

Redundancy

Also called data duplication, redundant

Redundancy is the presence or provision of duplicated or overlapping information, components, resources, or capabilities.

How 13 Manning books explain it

Machine Learning System Design

The condition in which multiple input features provide overlapping or duplicative information.

How it is used
Guides feature selection toward a small set of strong, diverse inputs rather than many correlated ones.
How deep it goes
Explains the performance risk of redundant features but does not specify a detection or selection method.
What you can do after
Evaluate feature sets for redundancy alongside predictive performance and implementation costs.

Read how Machine Learning System Design explains redundancy →

Think Like a CTO

Redundancy is the provision of duplicate or alternative components or paths so a system can continue operating when one fails.

How it is used
Frames redundancy as a cloud resilience and disaster-recovery decision shaped by acceptable downtime.
How deep it goes
Explains failure signs and two-zone recovery constraints, but stops short of a configuration procedure.
Examples
Uses cloud data loss, disruptive hardware failure, duplicate recovery servers, and database synchronization across geographic zones.
What you can do after
Evaluate/understand whether a proposed redundancy strategy can meet a chosen downtime tolerance at an acceptable cost and complexity.

Read how Think Like a CTO explains redundancy →

Fundamentals of Cybersecurity

Physical redundancy is the provision of alternate facilities or locations so operations can continue when a primary data center becomes unusable.

How it is used
Keeps data-center services available through component failures and supports continued operations when a primary site cannot be used.
How deep it goes
Defines duplicate components and compares availability targets and layered backups, but does not provide a procedure for engineering a redundant site.
Examples
Uses redundant power feeds, UPS batteries, generators, servers, and a flight-disrupting outage to show what backups protect and where recovery can falter.
What you can do after
Evaluate/understand how backup components and alternate sites reduce downtime, and weigh added availability against complexity and cost.

Read how Fundamentals of Cybersecurity explains redundancy →

Amazon Web Services in Action, Third Edition: An in-depth guide to AWS

Redundancy is the provision of multiple interchangeable components or paths so that failure of one does not interrupt service.

How it is used
Uses multiple components and paths to remove single points of failure in fault-tolerant web applications.
How deep it goes
Explains component replication, Availability Zones, decoupling, and replacement, but stops short of detailed configuration steps.
Examples
Uses multiple pie-production lines and EC2 instances distributed behind a load balancer.
What you can do after
Apply redundancy by distributing EC2 instances across Availability Zones and connecting them through load balancing or SQS.

Read how Amazon Web Services in Action, Third Edition: An in-depth guide to AWS explains redundancy →

The Art of Code

Redundancy is the provision of duplicate or alternative resources so a system can continue operating when one resource fails.

How it is used
Supports infrastructure resilience when parts of a system fail.
How deep it goes
Describes infrastructure recovery mechanisms at a high level without configuration details.
Examples
Uses load balancers, message queues, and Kubernetes restarts, traffic rerouting, and capacity scaling as infrastructure examples.
What you can do after
Evaluate redundancy’s role in infrastructure recovery alongside application-level resilience.

Read how The Art of Code explains redundancy →

Generative AI in Action

A redundancy strategy provides duplicate or alternate system resources so service can continue when a component fails or becomes unavailable.

How it is used
Supports reliable, scalable generative AI applications by keeping services available during component, endpoint, or regional failures.
How deep it goes
Connects redundancy to multi-region deployment, load balancing, failover, disaster recovery, testing, and monitoring without detailing recovery algorithms.
Examples
Uses multi-region model deployments, cloud load balancing, and multiple-model classifiers as concrete redundancy patterns.
What you can do after
Operate/configure production AI deployments with alternate resources, planned failover, recovery procedures, monitoring, and availability testing.

Read how Generative AI in Action explains redundancy →

Timeless Algorithms, The Foundational Ideas

Redundancy is the deliberate inclusion of repeated or structured information to enable reliable recovery of a message despite errors or noise.

How it is used
Frames redundancy as a tradeoff between efficient representation and reliable transmission under uncertainty.
How deep it goes
Explains compression and majority decoding, then states the channel-coding limit without detailing real code designs.
Examples
Uses AAAAAA, W7dX8$, and tripled YES to illustrate compression and recovery from errors.
What you can do after
Evaluate when redundancy can be removed for compression and when adding it improves recovery from transmission errors.

Read how Timeless Algorithms, The Foundational Ideas explains redundancy →

Quantization and Fast Inference

Model redundancy is the repeated encoding of information across a model's parameters, allowing some parameter perturbations without destroying the signal.

How it is used
Predicts whether post-training quantization can absorb quantization error without retraining.
How deep it goes
Names spare capacity as a PTQ-success factor but does not explain or quantify redundancy.
Examples
Illustrates a favorable PTQ case with a large CNN targeting INT8 under a 2% accuracy tolerance.
What you can do after
Evaluate whether PTQ may suffice by considering model size and redundancy alongside architecture, bit-width, and accuracy tolerance.

Read how Quantization and Fast Inference explains redundancy →

Starting Data Analytics with Generative AI and Python

A duplicate record is a repeated or substantially repeated data entry representing the same underlying observation.

How it is used
Removes repeated records during data cleaning to prevent overrepresenting observations and skewing analytical results.
How deep it goes
Works through exact-row removal and subset selection, while noting that paraphrased reviews need more sophisticated detection.
Examples
Demonstrates pandas removal on a two-column DataFrame and identifies exact or lightly altered duplicate reviews.
What you can do after
Apply pandas DataFrame.drop_duplicates() across all columns or a selected subset.

Read how Starting Data Analytics with Generative AI and Python explains redundancy →

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

Redundancy is the use of multiple equivalent instances or components so operation can continue when one fails.

How it is used
Maintains continuous microservice service during intermittent instance failures.
How deep it goes
Explains replication, load balancing, Kubernetes restarts, and deployment configuration, while deferring performance-focused replication.
Examples
Uses a gateway Deployment with three replicas and a load-balanced microservice infrastructure diagram.
What you can do after
Operate/configure Kubernetes Deployments with multiple replicas and diagnose failures without losing service continuity.

Read how Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform explains redundancy →

Delivering Machine Learning Projects: From design to deployment

Data duplication is the unintended presence of multiple copies of the same data record or content in a data resource.

How it is used
Checks pipelines and surveyed datasets for repeated records as part of data-quality testing and review.
How deep it goes
Names replay, loop-condition bugs, and manual copying as causes, but gives no specific deduplication procedure.
Examples
Uses source replay, faulty copying loops, manual pasting, and duplicate Bike Shop warehouse records as examples.
What you can do after
Diagnose duplicate records by checking pipeline data and flagging count discrepancies for investigation.

Read how Delivering Machine Learning Projects: From design to deployment explains redundancy →

Grokking Software Architecture

Redundancy is the provision of duplicate or alternate components or resources so a system can continue operating after a failure.

How it is used
Provides alternate compute, message, or data resources so operations can continue through component failures.
How deep it goes
Contrasts identical backups with diverse fallbacks, then distinguishes live replication from recoverable offline backups.
Examples
Uses Ariane 5's matching navigation computers, Apollo 13's Lunar Module, event queues, database replicas, and 3-2-1 backups.
What you can do after
Evaluate whether a backup avoids the original failure and align data copies with acceptable recovery time and data loss.

Read how Grokking Software Architecture explains redundancy →

ScyllaDB in Action

Redundancy is the inclusion of duplicate data or components so that a system can continue operating when one becomes unavailable.

How it is used
Supports continued requests and scaling when distributed data holders or components become unavailable.
How deep it goes
Explains duplicate copies, holder coordination, unavailable nodes, scaling, and response-count trade-offs.
Examples
Uses ABC Data employees, three data holders, an unavailable Charlotte, and one-, two-, or three-holder responses.
What you can do after
Evaluate how response requirements balance immediate availability against the newest available data.

Read how ScyllaDB in Action explains redundancy →

Also covered in

What to know first

Related concepts

Questions about redundancy

What is redundancy?

Redundancy is the presence or provision of duplicated or overlapping information, components, resources, or capabilities.

Which Manning books explain redundancy?

Machine Learning System Design, Think Like a CTO, Fundamentals of Cybersecurity, Amazon Web Services in Action, Third Edition: An in-depth guide to AWS, The Art of Code, Generative AI in Action, Timeless Algorithms, The Foundational Ideas, Quantization and Fast Inference and 5 more.

What should I know before learning redundancy?

Manning books that teach redundancy usually introduce reliability, language model, availability and load balancing first.

What kinds of redundancy are there?

Kinds of redundancy include semantic redundancy.

What is redundancy also called?

Redundancy is also called data duplication or redundant.

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.