New user asking for advice on database design

[David Boxenhorn <da...@lookin2.com>]

Hi guys! I'm brand new to Cassandara, and I'm working on a database design.
I don't necessarily know all the advantages/limitations of Cassandra, so I'm
not sure that I'm doing it right...

It seems to me that I can divide my database into two parts:

1. The (mostly) normal data, where every piece of data appears only once (I
say "mostly" because I think I need reverse indexes for delete... and once
it's there, other things).

2. The indexes, which I use for queries.

Questions:

1. Is the above a good architecture?
2. Would there be an advantage to putting the two parts of the database in
different keyspaces? I expect the indexes to change every once in a while as
my querying needs progress, but the normal database won't change unless I
made a mistake.

Any other advice?

Re: New user asking for advice on database design

[Zhiguo Zhang <mi...@gmail.com>]

do you have read the article "
WTF is a SuperColumn? An Intro to the Cassandra Data
Model<http://arin.me/blog/wtf-is-a-supercolumn-cassandra-data-model>"?
link: http://arin.me/blog/wtf-is-a-supercolumn-cassandra-data-model


it is a good article for data model.


On Thu, Apr 22, 2010 at 10:38 AM, Yésica Rey <ye...@gdtic.es> wrote:

> Hi David,
>
> I think your arquitecture is right. I'm also new in cassandra, and I ve
> designed my database similar than yours.
> I also think that division than data and indexes is more efficient in the
> queries.
>
> I had not raised your question about put them in a separated keyspaces, but
> I also appreciate any sugestion.
>
> Yess
>
> David Boxenhorn escribió:
>
>  Hi guys! I'm brand new to Cassandara, and I'm working on a database
>> design. I don't necessarily know all the advantages/limitations of
>> Cassandra, so I'm not sure that I'm doing it right...
>>  It seems to me that I can divide my database into two parts:
>>  1. The (mostly) normal data, where every piece of data appears only once
>> (I say "mostly" because I think I need reverse indexes for delete... and
>> once it's there, other things).
>>  2. The indexes, which I use for queries.
>>  Questions:
>>  1. Is the above a good architecture?
>> 2. Would there be an advantage to putting the two parts of the database in
>> different keyspaces? I expect the indexes to change every once in a while as
>> my querying needs progress, but the normal database won't change unless I
>> made a mistake.
>>  Any other advice?
>>
>

Re: New user asking for advice on database design

[Yésica Rey <ye...@gdtic.es>]

Hi David,

I think your arquitecture is right. I'm also new in cassandra, and I ve 
designed my database similar than yours.
I also think that division than data and indexes is more efficient in 
the queries.

I had not raised your question about put them in a separated keyspaces, 
but I also appreciate any sugestion.

Yess

David Boxenhorn escribió:
> Hi guys! I'm brand new to Cassandara, and I'm working on a database 
> design. I don't necessarily know all the advantages/limitations of 
> Cassandra, so I'm not sure that I'm doing it right...
>  
> It seems to me that I can divide my database into two parts:
>  
> 1. The (mostly) normal data, where every piece of data appears only 
> once (I say "mostly" because I think I need reverse indexes for 
> delete... and once it's there, other things).
>  
> 2. The indexes, which I use for queries.
>  
> Questions:
>  
> 1. Is the above a good architecture?
> 2. Would there be an advantage to putting the two parts of the 
> database in different keyspaces? I expect the indexes to change every 
> once in a while as my querying needs progress, but the normal database 
> won't change unless I made a mistake.
>  
> Any other advice?