incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ramesh S <investt...@gmail.com>
Subject Re: is it advisable to keep the data that is not frequently read/written to the database else where ?
Date Fri, 30 Sep 2011 16:18:41 GMT
Thank you Jonathan for your quick reply.
The reason I asked the question is because I have noticed some companies
have used Cassandra to store data (which needs frequent read writes )
in-memory and have used other databases for data which is less frequently
read/updated.
So this created my doubt in my design decision.
 Also we have a major portion of data which need not be in-memory . Right
now we have a design where everything is in the same keyspace.
So is there a way where we can may be swap that data, which is less
demanding , to disk , by keeping in a different keyspace.

Thanks
regards
Ramesh


On Fri, Sep 30, 2011 at 10:30 AM, Jonathan Ellis <jbellis@gmail.com> wrote:

> Short answer: no.
>
> Longer: What problems do you hope to avoid by adding this complexity?
>
> On Fri, Sep 30, 2011 at 9:45 AM, Ramesh S <investtrco@gmail.com> wrote:
> >
> >
> > I have some data that would be read/write might be once during the entire
> > session, like authentication info.
> > When designing database with Cassandra is it advisable to keep the data
> that
> > is not frequently read/written to the database else where ?
> >
> > Thank you
> > regards,
> > Ramesh
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support
> http://www.datastax.com
>

Mime
View raw message