<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: jason-sobel</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/jason-sobel.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2008-08-20T23:51:31+00:00</updated><author><name>Simon Willison</name></author><entry><title>Facebook engineering notes on Scaling Out</title><link href="https://simonwillison.net/2008/Aug/20/engineering/#atom-tag" rel="alternate"/><published>2008-08-20T23:51:31+00:00</published><updated>2008-08-20T23:51:31+00:00</updated><id>https://simonwillison.net/2008/Aug/20/engineering/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.facebook.com/notes.php?id=9445547199"&gt;Facebook engineering notes on Scaling Out&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Jason Sobel explains a couple of tricks Facebook use to deal with consistency between their California and Virginia data centres. The first is to hijack the MySQL replication stream to include information about memcached records to invalidate; the second is to use Layer 7 load balancers which inspect a “last modification time” cookie and send users to the masters in California if they have updated their profile in the past 20 seconds.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/facebook"&gt;facebook&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jason-sobel"&gt;jason-sobel&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/memcached"&gt;memcached&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/mysql"&gt;mysql&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/replication"&gt;replication&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/scaling"&gt;scaling&lt;/a&gt;&lt;/p&gt;



</summary><category term="facebook"/><category term="jason-sobel"/><category term="memcached"/><category term="mysql"/><category term="replication"/><category term="scaling"/></entry></feed>