ScaleArc
Load balancing software
- Features
- Ease of use
- Ease of management
- Quality of support
- Affordability
- Market presence
Take the quiz to check if ScaleArc and its alternatives fit your requirements.
Contact the product provider
Free Trial
Free version unavailable
Small
Medium
Large
- Retail and wholesale
- Banking and insurance
- Healthcare and life sciences
What is ScaleArc
ScaleArc is a database load balancing and proxy product designed to sit between applications and relational database clusters. It routes and balances database connections, provides health checks and failover handling, and can enforce policies such as read/write splitting depending on database topology. It is typically used by infrastructure and database teams to improve availability and connection management for MySQL and similar environments. The product focuses on database-aware traffic management rather than general-purpose HTTP load balancing.
Database-aware traffic routing
ScaleArc operates at the database connection layer and is designed for database-specific routing decisions rather than generic L4/L7 web traffic. It can direct connections based on database role (for example, primary vs. replicas) and health status. This makes it suitable for teams that need database-centric load balancing and failover behavior. It reduces the need to build custom routing logic into applications.
High availability and failover
The product includes health monitoring and can shift traffic away from unhealthy database nodes. It supports architectures where a proxy layer provides continuity during node failures or maintenance. This can simplify application connection strings by presenting a stable endpoint. It is commonly positioned for environments where database uptime and controlled failover are operational priorities.
Connection management and pooling
ScaleArc is used to manage large numbers of database connections and can help smooth connection spikes at the database tier. Centralized connection handling can reduce direct connection pressure on database servers. It also provides a control point for enforcing connection-related policies. This is particularly relevant for high-concurrency application stacks.
Narrower scope than ADCs
ScaleArc is specialized for database traffic and does not replace general-purpose load balancers used for HTTP(S), API gateways, or edge delivery. Organizations often still need separate tooling for web ingress, TLS termination, and content delivery. This can increase the number of components to operate. It fits best when database load balancing is a distinct requirement.
Database and topology constraints
Capabilities such as read/write splitting and failover behavior depend on supported database engines and the replication/failover topology in use. Some advanced behaviors may require specific clustering solutions or careful configuration to avoid consistency issues. Teams may need to validate compatibility with their database versions and HA tooling. Mismatches can limit the value of database-aware routing features.
Operational overhead for proxy layer
Introducing a database proxy adds another tier that must be deployed, monitored, and scaled. Misconfiguration can affect application connectivity or introduce latency if not sized appropriately. High availability for the proxy itself typically requires redundant instances and careful failover design. This adds operational work compared with simpler direct-to-database connection patterns.
Plan & Pricing
No public pricing listed on the vendor site. Official ScaleArc / IgniteTech pages reference licensed editions (example: "Platinum") and license parameters (maximum ScaleArc cores, vCPUs, clusters, cache) but do not publish plan prices or tier rates. Official guidance is to contact ScaleArc/IgniteTech sales for purchase or production licensing. Notes:
- Documentation mentions an "evaluation" (pre-installed ScaleArc for evaluation) that must be upgraded to a production license to continue use.
- Licensing appears to be edition- and capacity-based (licenses tied to CPU cores, vCPUs, clusters, cache), not a publicly listed per-user/month plan.
Seller details
NetApp, Inc.
San Jose, CA, USA
1992
Public
https://www.netapp.com/
https://x.com/netapp
https://www.linkedin.com/company/netapp/
