From: Marcos Ortiz <mlortiz@uci.cu>
To: Ross Reedstrom <reedstrm@rice.edu>
Cc: pgsql-performance@postgresql.org
Subject: Re: AppScale backend datastore (NoSQL again kind of)
Date: Thu, 13 Sep 2012 14:30:16 -0400
Message-ID: <50522638.3090008@uci.cu> (raw)
In-Reply-To: <20120913181113.GB26745@rice.edu>
References: <20120913181113.GB26745@rice.edu>
Regards, Ross.
Dimitri Fontaine gave a excellent talk in the last PgCon about the
migration of Fotolog from MySQL to
PostgreSQL with amazing advices around this, so you can contact him for
his advice.
On 09/13/2012 02:11 PM, Ross Reedstrom wrote:
> Hey PostgreSQL speed demons -
> At work, we're considering an AppScale deployment (that's the Google App Engine
> roll-your-own http://appscale.cs.ucsb.edu/). It supports multiple technologies
> to back the datastore part of the platform (HBase, Hypertable, MySQL Cluster,
> Cassandra, Voldemort, MongoDB, MemcacheDB, Redis). Oddly enough, in performance
> tests, the MySQL Cluster seems like the general winner (their tests, we haven't
> done any yet)
>
> So, my immediate thought was "How hard would it be to replace the MySQL
> Cluster bit w/ PostgreSQL?" I'm thinking hot standby/streaming rep. May or may
> not need a pooling solution in there as well (I need to look at the AppScale
> abstraction code, it may already be doing the pooling/direction bit.)
It depends of many factors:
- size of the MySQL cluster
- size of the involving data, etc
For the pooling solution, I recommend you to see PgBouncer, it´s a great
project widely used for this topic.
>
> Any thoughts from those with more experience using/building PostgreSQL clusters?
> Replacing MySQL Cluster? Clearly they must be using a subset of functionality,
> since they support so many different backend stores. I'll probably have to
> set up an instance of all this, run some example apps, and see what's actually
> stored to get a handle on it. The GAE api for the datastore is sort of a ORM,
> w/ yet another query language, that seems to map to SQL better than to NoSQL,
> in any case. There seems to be a fairly explicit exposure of a table==class
> sort of mapping.
>
> Ross
Best wishes
--
Marcos Luis Ortíz Valmaseda
*Data Engineer && Sr. System Administrator at UCI*
about.me/marcosortiz <http://about.me/marcosortiz;
My Blog <http://marcosluis2186.posterous.com;
Tumblr's blog <http://marcosortiz.tumblr.com/;
@marcosluis2186 <http://twitter.com/marcosluis2186;
10mo. ANIVERSARIO DE LA CREACION DE LA UNIVERSIDAD DE LAS CIENCIAS INFORMATICAS...
CONECTADOS AL FUTURO, CONECTADOS A LA REVOLUCION
http://www.uci.cuhttp://www.facebook.com/universidad.ucihttp://www.flickr.com/photos/universidad_uci
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mlortiz@uci.cu, reedstrm@rice.edu
Subject: Re: AppScale backend datastore (NoSQL again kind of)
In-Reply-To: <50522638.3090008@uci.cu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox