liveBook · Manning

Redundancy

As explained in Generative AI in Action

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

Redundancy keeps a generative AI application available by providing duplicate or alternate resources when a component fails or becomes unavailable. In production, it supports reliable service across retrievers, models, regions, and deployment environments. section 8.4.1 section 11.1

Apply redundancy alongside the mechanisms that make alternate resources usable:

  • Deploy model services across multiple regions so the application can continue operating if one region becomes unavailable. section 10.5.1
  • Combine redundancy with load balancing, API gateways, queuing, and stream processing to distribute traffic and manage demand spikes. section 10.5.1
  • Plan failover and disaster recovery, then validate model performance, system health, and recovery behavior through regular testing and monitoring. section 11.1 section 11.7
  • Balance availability against infrastructure requirements, operational complexity, and deployment cost when selecting virtual machines, containers, or serverless functions. section 11.2 section 11.7

Multi-model and multi-region service

A generative AI application can route requests among multiple model endpoints and deploy those services across regions. If one endpoint or region fails, routing and gateway controls can direct traffic to an available alternative. section 10.5.1 section 11.2

Figure 10.5 Classifier using multiple models
figure

Visualizes a classifier architecture that uses multiple models and routes questions according to intent, illustrating alternate model resources within an application. section 10.5.1

How Generative AI in Action covers it

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 it assumes
Assumes familiarity with generative AI application deployment and introduces redundancy through practical architecture and production-planning concerns.
What you can do after
Operate/configure production AI deployments with alternate resources, planned failover, recovery procedures, monitoring, and availability testing.
How it connects
Ties redundancy to scalability, load balancing, model ensembles, failover, disaster recovery, monitoring, and API gateways.

Also explained in

Compare how 6 books explain redundancy →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Generative AI in Action. The section links point to the parts of the book it draws on.