Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of tsaloranta@gmail.com
 designates 209.85.217.214 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=rA50wTPiSriUAgAEuik/36KIYLlUAe1Q14FePqF2uf8+QQO+15mrxKNi+mfuKmSCGk
         17BIBFIqki7IXumA78p++LAsnmKxvW2Qe/oY7/hKIcgfxk3hQXTf0Z1OJa9fxwVkZSt/
         6FTox+2MOjt5xYSnyqGaL0/x1iVhS/3NF9Zmw=
MIME-Version: 1.0
In-Reply-To: <4BD5CEF5.70500@endpoint.com>
References: <i2s6b59c1821004261026r35eb990aic15334b3c52ccbe2@mail.gmail.com>
	 <4BD5CEF5.70500@endpoint.com>
Date: Mon, 26 Apr 2010 12:11:57 -0700
Message-ID: <k2o5f7770581004261211sfe1f5df3qd4c72f9652859e93@mail.gmail.com>
Subject: Re: ORM in Cassandra?
From: Tatu Saloranta <tsaloranta@gmail.com>
To: user@cassandra.apache.org, ethan@endpoint.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 26, 2010 at 10:35 AM, Ethan Rowe <ethan@endpoint.com> wrote:
> On 04/26/2010 01:26 PM, Isaac Arias wrote:
>>
>> On Apr 26, 2010, at 12:13 PM, Geoffry Roberts wrote:
>>
...
>> In my opinion, a mapping solution for Cassandra should be more like a
>> Template. Something that helps map (back and forth) rows to objects,
>> columns to properties, etc. Since the data model can vary so much
>> depending on data access patters, any overly structured approach that
>> prescribes a particular schema will be of limited use.
>>
> For what it's worth, this is exactly my opinion after looking at the prob=
lem
> for a bit, and I'm actively developing such a solution in Ruby. =A0I spen=
t
...
> So, for my approach, there's one project that gives metaprogramming
> semantics for building the mapping behavior you describe: build classes t=
hat
> are oriented towards mapping between simple JSON-like structures and
> full-blown business objects. =A0And a separate project that layers Cassan=
dra
> specifics on top of that underlying mapper tool.

+1

I think proper layering is the way to go: it makes problem (of simple
construction of services that use Cassandra as the storage system)
much easier to solve, divide and conquer. There are pretty decent
OJM/OXM solutions that are mostly orthogonal wrt distributed storage
part. I understand that there are some trade-offs (some things are
easiest to optimize when Cassandra core handles them), but flexibility
and best-tool-for-the-job have their benefits too.

-+ Tatu +-