Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of Abhinandan.Prateek@citrix.com
 designates 203.166.19.134 as permitted sender)
From: Abhinandan Prateek <Abhinandan.Prateek@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
CC: Min Chen <min.chen@citrix.com>, Alex Huang <Alex.Huang@citrix.com>
Date: Fri, 14 Dec 2012 11:12:16 +0530
Subject: Re: Does anybody try nosql-on-mysql?
Thread-Topic: Does anybody try nosql-on-mysql?
Thread-Index: Ac3Zvcfx02/A4P3qT9yyrICHsvxytQ==
Message-ID: <CCF0B7FD.14663%abhinandan.prateek@citrix.com>
In-Reply-To: 
 <C66C814C1ABFA8449FF65CB44953A8B4012CBF3A56BF@SJCPMAILBOX01.citrite.net>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.5.121010
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

This is a good start and we should look for various options to speed up
the db access.

For cloudstack ACID compliance is important and some of these solutions
achieve speed by trading off ACID properties. So I guess complete
replacement of SQL may not be possible.

There is another option of using nosql like Redis to cache the mysql query
data. Again we need to see the complexity of using the native memcached
API Vs simplicity of the nosql db to do caching.


-abhi


On 14/12/12 10:52 AM, "Edison Su" <Edison.su@citrix.com> wrote:

>Looks like, the nosql-on-mysql
>(http://dev.mysql.com/tech-resources/articles/whats-new-in-mysql-5.6.html#
>nosql) an ideal solution for cloudstack API layer.
>"Using the memcached API, web services can now directly access the InnoDB
>storage engine without transformations to SQL, ensuring low latency and
>high throughput for read/write queries."
>Isn't what we want for api layer?