In a previous post I wrote about how read/write split is implemented in ProxySQL, and what I believe is the best practice for read/write split on top of MySQL servers: start sending all traffic to MySQL master identify what queries can be routed to the MySQL
While me and Fred were presenting Inexpensive Datamasking for MySQL with ProxySQL at FOSDEM 2017, we got a very interesting question: can ProxySQL be used to ob
Query routing is one of the core features of ProxySQL. Read/write split is perhaps one of the most common query routing use, while the other most commonly used
Since its genesis ProxySQL was designed to be reconfigurable at runtime without restarting it. There are only 2 exceptions: changing the listening ports (work i
Few days ago MariaDB announced MaxScale 2.1.0 Beta, and among the new Query Performance capabilities there is Query Cache Filter. Query Cache was among the very
Few days ago MariaDB announced that MaxScale 2.1 is roughly 45% faster than MaxScale 2.0 . I first want to congratulate MaxScale Team: MaxScale 2.1 seems to
Last month, January 2017, two DevOps meetups were organized in Spain with the same topic: "Conociendo ProxySQL", presented by txetxu Velayos, @txetxuvel The
MySQL Group Replication is a hot topic in MySQL ecosystem. We have been evaluating it in , and it is now time to evaluate its performance, especially now that i
MySQL load balancers and proxies are becoming a very hot topic in the last few years. In the near future there will two presentations to compare proxies: T
One of the most common requests for ProxySQL is to support Galera Cluster. The Issue Support for Galera requires a lot of features to be added to ProxySQL:
One of ProxySQL most interesting features is query rewrite. This functionality is one of the main reasons to write a proxy that sits between the applicatio
A benchmark comparison of ProxySQL and MaxScale focusing on persistent connections, throughput, response time, and critical session-tracking bugs in MaxScale's implementation.
Showing 61–72 of 72 posts