Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of mpeters@plusthree.com
 designates 207.254.216.11 as permitted sender)
Message-ID: <4F86E132.70501@plusthree.com>
Date: Thu, 12 Apr 2012 10:05:38 -0400
From: Michael Peters <mpeters@plusthree.com>
User-Agent: Mozilla/5.0 (X11; Linux i686;
 rv:11.0) Gecko/20120329 Thunderbird/11.0.1
MIME-Version: 1.0
To: Clinton Gormley <clint@traveljury.com>
CC: Jim Schueler <jschueler@eloquency.com>, modperl@perl.apache.org
Subject: Re: highscalability.com report
References: <4F7B6638.10800@web.de>
  <alpine.LRH.2.00.1204031909050.15976@server.tqis.com>
 <1334239242.13300.1.camel@balrog.traveljury.com>
In-Reply-To: <1334239242.13300.1.camel@balrog.traveljury.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 04/12/2012 10:00 AM, Clinton Gormley wrote:

> I think the bigger factor in the speed improvement is probably to do
> with switching from MySQL to Redis
>
> https://groups.google.com/group/redis-db/browse_thread/thread/77841c595d29f983?pli=1

They didn't really "switch" from mysql to redis. They are using Redis as 
a structured caching layer in front of mysql. Their authoritative data 
is still stored in mysql, but they have several "views" of that data 
that they export regularly to redis. The site pulls these cached views 
from redis and yes that's very fast.

It's kind of similar to a lot of other really big systems (like 
facebook). Authoritative data in an SQL database and then their read 
data in denormalized structures in a NoSQL database.

-- 
Michael Peters
Plus Three, LP