Skip to main content

Overview

As your voice agent grows, you’ll need to scale to handle more concurrent conversations. This guide covers practical scaling strategies.

Vertical Scaling

Increase Resources

Start by adding more resources to your existing server:
When to use:
  • Conversation volume growing but manageable
  • Simple to implement
  • Cost-effective for moderate growth
Limits:
  • Single server can only scale so far
  • No redundancy

Horizontal Scaling

Multiple Instances

Run multiple agent instances:
Benefits:
  • Handle more concurrent conversations
  • Built-in redundancy
  • Easy to scale up/down

Load Balancing

Distribute conversations across instances:

Auto-Scaling

Kubernetes Horizontal Pod Autoscaler

Automatically scale based on load:
This will:
  • Start with 2 instances minimum
  • Scale up to 10 instances maximum
  • Add instances when CPU > 70%
  • Remove instances when CPU < 70%

Performance Optimization

Connection Pooling

Reuse database connections:

Caching

Cache frequently accessed data:

Monitoring Capacity

Track Key Metrics

Monitor these metrics to know when to scale:

Best Practices

1. Start Small, Scale as Needed

2. Set Conversation Limits

3. Monitor and Alert

Scaling Checklist

When scaling your agent:
  • Set up health checks
  • Configure auto-scaling rules
  • Set resource limits
  • Enable monitoring
  • Test with load testing
  • Document scaling procedures

Next Steps

Deployment

Deploy your agent

Monitoring

Monitor your agent