Mysql-Proxy pour ou contre ?

Posted on

L’arrivé de Mysql-Proxy se veut comme un tournant dans la gestion de la haute disponibilité des bases de données. Cependant quel en est le retour. Pour teste mysql-proxy ( 0.8.1 ) toujours en alpha release c’est ici : http://dev.mysql.com/downloads/mysql-proxy/.

Mysql-proxy est bon pour plusieurs petites choses voici un panel des différentes scénarios possibles
Cependant il n’est pas à utiliser en production car trop jeune !!!

Query: Interception 147 (27.1%)
Query: Rewriting 135 (24.9%)
Query: Injection 112 (20.6%)
Query: Logging 150 (27.6%)
Query: Analysis 173 (31.9%)
Query: Auditing 109 (20.1%)
Query: Sniper 72 (13.3%)
Query: Patroller 78 (14.4%)
Load Balancing: Read/Write Splitting 307 (56.5%)
Load Balancing: Server Least Loaded 221 (40.7%)
Load Balancing: Server with best Response Time 152 (28.0%)
Load Balancing: Least Open Connections 126 (23.2%)
Load Balancing: Weighted Round Robin 141 (26.0%)
Load Balancing: Select IPs, ranges or named hosts 116 (21.4%)
Sharding: Application Partitioning Awareness 163 (30.0%)
Auditing: Capturing Selects/Reads/DML/DDL 78 (14.4%)
Change Management 80 (14.7%)
Capacity Planning 98 (18.0%)
Connection: Concentration 91 (16.8%)
Connection: Pooling 190 (35.0%)
Connection: Throttling 82 (15.1%)
HA: Fail over between Proxies 230 (42.4%)
HA: Assist in Replication Fail over 186 (34.3%)
HA: Resynch Master after failure 191 (35.2%)
Performance: Built-in cache functionality 202 (37.2%)
Performance: Transmission compression 128 (23.6%)
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s