Scaling Recommendations


This guide outlines best practices for scaling dbWatch Control Center deployments in complex or growing environments.

Scaling may be necessary when:


Recommended Instance Hub Ratio

Each Instance Hub should typically manage up to 200–250 database instances for optimal performance and maintainability.

If managing more, consider:

In large deployments, the Domain CA (certificate authority) should run on a separate system from the Instance Hub to distribute trust responsibilities and improve security.


Recommended Cloud Router Architecture

In deployments with:

It is strongly recommended to:

See:


Scale by Role Separation

Separate key responsibilities across nodes for better scalability and control.

Role Recommendation
Monitor Client Deploy multiple clients near end-users or regional teams
Instance Hub 1 per ~200–250 instances; separate per zone if possible
Domain CA Place on dedicated system in larger deployments
Dashboard / Web Separate node or co-located with low-load hub
CCC Script Node Use restricted-privilege node: Scripting Node with Limited Privileges

Efficient Instance Deployment and Job Consistency

In large environments, avoid manually installing database instances one-by-one through the GUI wizard, as this is time-consuming and error-prone.

Instead, use one of the following:


Job Load & Performance Tuning


Certificate and Routing Considerations


Monitoring at Scale


Multi-Domain Strategy

For use cases such as MSP environments or regulatory isolation:


Related Topics