基于Node.js的分布式MySQL代理服务.pdfVIP

•Node.js-based •Distributed MySQL Proxy 王达心 @daxin11 2012/09 About Me • sina, distributed platform dev • 5 years+ C++ Experiences • Using node.js no more than 1 year, No experience with JS • Last company: Baidu, Automatic DevOps Platform, Monitoring Platform Page 2 of 41 contents  What’sthe problem  Platform Architecture  Proxy functionalities and features  Design of Proxy  Why Node.js?  Performance  Node.js weaknesses  Used module and experiences Page 3 of 41 What’s the problem • MySQL is still most reliable and popular in large scale applications • Sharding of data is tightly-coupled with MySQL server deployment • Resources waste in small applications • Inefficient Ops with mass MySQL servers Page 4 of 41 Platform Architecture Page 5 of 41 Proxy functionalities and features • Totally compatible with MySQL network protocal • Sharding transparent to applications • Separation of read and write • Load balance – Random select read server, weight supported – Hash by IP • DB failure decision by Multi node, auto switchover Page 6 of 41 Design of Proxy • Sharding transparent to applications – Map rowkey to N tables – Divide N to M ranges, each map to a DB group(1master /n slaves) – Divide each range when expanding • MySQL long connection pool – Pool for each Database – Init connection params by configuration • Don’t parse data of MySQL response, only transfer Page 7