ProxySQL
A high-performance, high-availability proxy for MySQL and PostgreSQL with advanced routing, caching, and load balancing.
What is ProxySQL?
ProxySQL is a high-performance, high-availability proxy for MySQL and PostgreSQL databases. It acts as an intermediary layer that manages database traffic, providing features like query routing, load balancing, caching, and connection pooling to improve scalability, reliability, and performance without modifying applications or databases.
Database administrators, DevOps engineers, and developers managing scalable MySQL or PostgreSQL deployments who need to optimize performance, ensure high availability, and simplify database operations.
Developers choose ProxySQL for its open-source flexibility, robust feature set, and SQL-based configuration that allows real-time adjustments without downtime, making it a powerful alternative to commercial database proxies.
Overview
High-performance proxy for MySQL and PostgreSQL
Use Cases
Best For
- Splitting read and write queries across database replicas
- Reducing database load with intelligent query caching
- Implementing automatic failover for high-availability database clusters
- Managing connection pooling to handle high-concurrency applications
- Enforcing security and access policies at the proxy layer
- Load balancing traffic across multiple database servers
Not Ideal For
- Environments using NoSQL databases like MongoDB or Cassandra
- Small-scale applications with a single database server and low traffic, where proxy overhead isn't justified
- Teams that prefer graphical user interfaces over SQL-based configuration
- Cloud-native deployments relying on fully managed database services with built-in proxy features
Pros & Cons
Pros
Built to address the lack of open-source high-performance proxies, as stated in the introduction, ensuring efficient handling of database traffic.
Allows online configuration changes via an admin SQL interface without restarting, enabling real-time adjustments for flexibility.
Supports MySQL, PostgreSQL, and their forks like Percona Server and MariaDB, providing versatility across common database systems.
Includes query routing, caching, load balancing, and failover handling from the key features, enhancing scalability and availability.
Cons
Configuration requires deep understanding of SQL commands and database protocols, as shown in the admin interface examples, which can be daunting.
Management is solely through command-line SQL interfaces or config files, lacking graphical tools that might simplify operations for some users.
Requires detailed configuration for servers, users, and query rules via files or SQL, as illustrated in the config file sections, adding to deployment time.
Frequently Asked Questions
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.