WHO ARE YOU???

WHO ARE YOU???• Clint Alexander• Lancaster County, PA• Married, 3 Children

2

MYSQL-PROXY: THE PROXY BELT

Clint Alexander <[email protected]>

• Internet Technologist• IT Contractor• 10 year Professional• MySQL Power User

Web Administration

Web Application Developer

Network Architect

Brainbench CIPCertified Internet Professional

PHP

Systems Administration

Perl

Interactive Developer

LuaLingo

Expect

Action ScriptVisual Basic

Project Management

3



WHY ARE WE HERE?

WHY ARE WE HERE?TO DESIGN FAIL-SAFE SYSTEMS

4




5



WHAT IS THAT?


6



WHAT IS THAT?HIGH AVAILABILITY!


7




uhh…


8




uhh…Keeping your services available 99.9% OF THE TIME.


9




uhh…Keeping your services available 99.9% OF THE TIME.

oh…

10



LET’S SET SOME REQUIREMENTS…

11

Maximize Cost-Effectiveness



12

Design Simple Management



13

Redundancy & Fail-Over



14

Maintain Optimal Performance



15

Minimize Dependencies



16

No Single Point of Failure



WHAT’S THE OBJECTIVE?

17

• Maximize Cost-Effectiveness• Design Simple Management• Create Redundancy & Fail-Over• Maintain Optimal Performance• Minimize Dependencies• No Single Point of Failure



LET’S TALK SCALING

18



19


SCALING UP


20



=

21



= More RAM= Fast CPU= Fast SCSI= Fast Bus

22



Result?

23


SUPER DUDE!(err… Server)


24



SCALING OUT

25



Take 1 fish…

26



Add lots more.

27



Standard Web

Service Setup

28



Where should requests go now?

29



SimpleScale-OutSolution

30



Requests still fulfilled

(whew!)

31


SINGLE GATEWAY DESIGNS

SPOF DETECTED!Single Point of Failure

Great For

• Development Networks• Low-Visibility Services• Low-Availability Services


32


DUAL GATEWAY DESIGNS

SOFTWARE REQUIRED!•Heartbeat Service•Switching Mechanism

Great For

• Production Networks• High-Visibility Services• High-Availability Services


33


THE PROXY BELT


“Strap-On” MySQL-Proxy

34


AUTONOMOUS DESIGN


Self-Reliant Systems

35


• Maximize Cost-Effectiveness• Design Simple Management• Redundancy & Fail-Over• Maintain Optimal Performance• Minimize Dependencies• No Single Point of Failure


REQUIREMENTSREQUIREMENTSREVIEWREVIEW

What’s the objective?

36


COST-EFFECTIVENESS?

• No Additional Hardware• No Additional

Installations• No Additional Software• No Additional Labor

Saving $5K – $10K


37


Maximum Cost-Effectiveness• Simple Management• Redundancy & Fail-Over• Maintain Optimal Performance• Minimize Dependencies• No Single Point of Failure



38


DESIGN SIMPLE MANAGEMENT?

• Servicing the Clients Relative to the purpose and configuration of

the clients• Servicing MySQL

Multiple GUI Administration Options• Servicing Proxy

Easy & Minimal Configuration

Simple Management, in this case, means management of a service required within the network is minimized by its lack of dependents and complexity of its configuration.


39


REQUIREMENTS REVIEW

Maximum Cost-EffectivenessSimple Management• Redundancy & Fail-Over• Maintain Optimal Performance• Minimize Dependencies• No Single Point of Failure


40


REDUNDANCY & FAIL-OVER?

• Failure to Client Server DNS Round-Robin (other?)


• MySQL Services Managed by Lua & Proxy connection

pooling

• Failure to Proxy Service Crontabs and Notifications!

41


Maximum Cost-EffectivenessSimple ManagementRedundancy & Fail-Over• Maintain Optimal Performance• Minimize Dependencies• No Single Point of Failure



42


MAINTAIN OPTIMAL PERFORMANCE?

• MySQL Proxy is light-weight and transparent

• Lua is a well-known light-weight API

Footprint = 0 (zero)


43


Maximum Cost-EffectivenessSimple ManagementRedundancy & Fail-OverMaintain Optimal Performance• Minimize Dependencies• No Single Point of Failure



44


MINIMIZE DEPENDENCIES?

• Users are dependent on available client systems

• Clients are dependent on available Proxy services

• Proxy is dependent on available MySQL servers

No Extra Dependencies RequiredClint Alexander <[email protected]>

45


Maximum Cost-EffectivenessSimple ManagementRedundancy & Fail-OverMaintain Optimal PerformanceMinimize Dependencies• No Single Point of Failure



46


NO SINGLE POINT OF FAILURE?

• Fail-over Requires: Minimum: 2+ Clients Minimum: 2+ Proxies Minimum: 2+ Databases


47


Maximum Cost-EffectivenessSimple ManagementRedundancy & Fail-OverMaintain Optimal PerformanceMinimize DependenciesNo Single Point of Failure


That’s the objective!

48


WAIT!!DIDN’T WE SAY SOMETHING ABOUT

A CRON SCRIPT?


49


MANAGABLE CONFIGURATION FILEAssumed Location: /etc/mysql-proxy/mysql-proxy.conf


50


CRON SCRIPT

Assumed Location: /opt/mysql-proxy/sbin/proxychk.cron


51


STARTUP SCRIPT

Assumed Location: /etc/init.d/mysqlproxy


52Clint Alexander <[email protected]>


http://www.cdalexander.net/mysql.php

Want a copy?

All material is or will be posted here.

Feel free to contact me directly:Clint Alexander <[email protected]>

WHO ARE YOU???

Documents

Transcript of WHO ARE YOU???