MySQL, memcached and replication

Here is a very interesting post from Facebook’s Jason Sobel on how Facebook is keeping up with their massive growth (more than 2 million new members each week. wow!) using a combination of MySQL, Memcached and a custom replication module they have created. Very nice.

Whenever that person goes to change some data—uploading a photo album, or changing profile info for example—we send them off to California so that all our modifying operations happen in the same location. This decision was made to prevent two or more modifications from conflicting with each other and messing up our data. It might sound like we’re forcing our users to go to California a lot but only about 10% of our traffic causes a modifying operation. MySQL has a great replication feature that allows us to, in real time, stream all the modifications happening on a California MySQL server to another one in Virginia. Replication happens so fast, even across the country, that the Virginia servers are almost never more than one or two seconds behind the California servers.

We have been using the same MySQL+memcached combination for the back end feeddo services and have been happy with the results. Sometimes Open Source feels like magic!

Author: @feedly

Read more. Know more.

One thought on “MySQL, memcached and replication”

Comments are closed.