In the past years combining MySQL with memcache focused on ‘use TRIGGERs and a memcache UDF’ or ‘do it in the app’. While one scales better and is transparent, the other is consistent.
Since MySQL 5.1 the row-based replication protocol contains all the properties to get scalability and consistency at the same time. Consistency we get by making sure the data reached a slave before we invalidate the data in memcache, scalability by keeping the query-execution free of syncronous, possibly blocking triggers.
All we need is a protocol translator which understands the MySQL replication protocol, can connect to as slave to the replication tree, filter the changes of the right tables and invalidate the data in memcache. … and the MySQL Proxy is our foundation.
Jan Kneschke works for Sun as Senior Software Developer in the MySQL Enterprise Tools team and maintains the MySQL Proxy and the agent component of MySQL Enterprise Monitor.
His favourite programming language is Lua as you can see in the
For information on exhibition and sponsorship opportunities at the conference, contact Yvonne Romaine at email@example.com
For media-related inquiries, contact Maureen Jennings at firstname.lastname@example.org
To stay abreast of conference news and to receive email notification when registration opens, please sign up for the O'Reilly MySQL Conference newsletter (login required).
View a complete list of O'Reilly MySQL Conference contacts.