For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Ask AIPlaygroundLoginFree API Key
HomeAPI ReferenceVoice AgentSpeech-to-TextText-to-SpeechIntelligenceSelf-Hosted Deployments
HomeAPI ReferenceVoice AgentSpeech-to-TextText-to-SpeechIntelligenceSelf-Hosted Deployments
    • Introduction
    • Deployment Environments
  • Amazon SageMaker
  • Docker/Podman
    • Drivers and Container Orchestration Tools
  • Kubernetes
    • Securing Your Cluster
    • Troubleshooting
  • Deployment
    • Self Service Licensing & Credentials
    • Deploy STT Services
    • Deploy Flux Model (STT)
    • Deploy TTS Services
    • Deploy Voice Agent
    • Status Endpoint
    • Certificate Status
  • Partner Deployment
  • Scaling and Deployment Strategies
    • System Maintenance
    • Blue-Green Deployment
    • Auto-Scaling
    • Metrics Guide
    • Ingress Authentication
    • Redact Usage
    • Log Formats
    • Using Private Container Registries
  • Features
    • Smart Formatting
  • Self-Hosted Add Ons
    • License Proxy
    • Prometheus Integration
    • Deepgram UniMRCP Plugin
  • Tools
    • Validate Deepgram Self-Hosted TTS
    • Using SDKs with Self-Hosted
LogoLogo
Ask AIPlaygroundLoginFree API Key
On this page
  • How It Works
  • Benefits
  • When to Use Blue-Green Deployment
  • Architecture
  • What’s Next
Scaling and Deployment Strategies

Blue-Green Deployment

Blue-green deployments are an effective strategy for managing self-hosted updates, especially in cases when backwards compatibility is not maintained and multiple container dependencies exist.

Was this page helpful?
Previous

Auto-Scaling

Auto-scaling is a complex endeavor. It is highly dependent on the application deployed, the use case of that application, and business needs and constraints. As such, this guide does not attempt to address all scenarios. A basic understanding of containerized infrastructure is assumed, and specific implementation details are out of scope save for some selected example configurations. References to other materials may also be provided where appropriate.

Next
Built with

Blue-green deployments involve maintaining two identical production environments during updates. The Blue deployment represents the current production environment serving live traffic, while the Green deployment represents the new version to be released.

This strategy is particularly effective when backwards compatibility is not maintained between versions or when multiple container dependencies must be updated together. By deploying changes to the inactive environment first, you can test and verify updates in a production-like setting without impacting end-users.

How It Works

  1. Deploy to Green Environment: Deploy the new version to the currently-unused Green environment, while Blue continues serving production traffic
  2. Test and Verify: Thoroughly test the Green environment to ensure it functions correctly without impacting users
  3. Route Traffic: When ready, route incoming requests to the Green environment with zero downtime
  4. Monitor: Closely monitor the Green environment for any issues after traffic begins flowing to it
  5. Rollback or Commit: If issues arise, instantly rollback to Blue; if stable, promote Green to production and decommission Blue

Benefits

  • Zero Downtime: Traffic switching happens instantly without service interruption
  • Instant Rollback: If problems occur, reverting to the previous version is immediate
  • Safe Testing: Test the new deployment in a production-identical environment
  • Risk Reduction: Minimize operational risk during updates with a clear fallback plan

When to Use Blue-Green Deployment

Consider using blue-green deployment when:

  • Deploying updates with breaking changes between API, Engine, and/or License Proxy containers
  • Multiple container dependencies must be updated together
  • Backwards compatibility cannot be maintained between versions
  • Zero-downtime updates are required for production systems

Architecture

What’s Next

Now that you understand blue-green deployment strategies, explore related topics:

  • System Maintenance - Updating and maintaining your deployment
  • Auto-scaling - Scaling your deployment based on demand
  • Metrics Guide - Monitoring your deployment health