The document discusses the overview, architecture, and features of mysql-proxy. Mysql-proxy sits between applications and databases, allowing for load balancing, connection management, and query filtering/modification through an embedded Lua scripting language. Key features include read-only splitting, access control, statistics gathering, and a programmable admin interface.

1. LSPE @Yahoo mysql-proxy By Farhad Saberi - Overview and architecture - Making The case for a proxy - Lua - Lua examples - The admin interface - currently known issues

2. Overview and Architecture Same idea as any other proxy. Sits between the application and its Database:

3. Overview and Arhitecture Read only Load Balancing with multiple –proxy-read-only-backend-addresses option

4. Making The case for mysql-proxy Easier sites management. Hundreds of connection definitions use the same host and port. DB Host connection changes are done at one place only.

5. No need to restart for configuration or behavioral changes. It all happens in real time.

6. Making the case for mysql-proxy Flexible, Powerful and invisible: intercept, tokenize and modify queries

7. Deny/allow queries based on DB or DB User.

8. Deny/allow based on a regex

9. Construct your own results set and return it to the application without ever actually querying the backend database.

10. LUA embedded

11. Making the case for a proxy It's fast and stable: Small daemon, about 35 MB in VSZ compared to a preforked apache child being 50 to 100 MB.

12. Coded in C

13. implements connection pooling

14. Doesn't need to do NS lookups every time

15. Has never “crashed” on me so far!

16. Making the case for mysql-proxy Open source.

17. LUA Simple scripting language

18. Small: its whole distribution fits in a floppy disk.

19. Extensible; it is easy to interface with C code.

20. LUA Widely used in games: