We've struggled getting consistent write latency & linear write
scalability with a pretty heavy insert load (1000's of records/second),
and our records are about 1k-2k of data (mix of integer/string columns
and a blob). Wondering if you have any rough numbers for your "small to
medium write si
Indeed I did not really compare C* operational simplicity to traditional
RDBMS. Implicity the comparison is made with other NoSQL datastore.
On Wed, Jul 9, 2014 at 2:51 AM, Robert Coli wrote:
> On Fri, Jul 4, 2014 at 2:10 PM, DuyHai Doan wrote:
>
>> c. operational simplicity due to master-les
I agree, that traditional RDBMS have good and established admin/mgmt
tools/practices.
But C* strength is distributed, failure tolerant operation. And this is exactly
where nearly all traditional RDBMS just fail. I've seen both Oracle and IBM
"clusters"/"HA" "solutions" (and a lot of other soft
AM
To: user@cassandra.apache.org
Subject: Re: Cassandra use cases/Strengths/Weakness
Hi,
i am a bit confused if cassandra is a choice for my use case especially after
reading this thread.
Is cassandra only for use cases with data load > 100TB and massive user counts?
What about all the
I've used various databases in production for over 10 years. Each has
strengths and weaknesses.
I ran Cassandra for just shy of 2 years in production as part of both
development teams and operations, and I only hit 1 serious problem
that Rob mentioned. Ideally C* would have guarded against it, b
On Fri, Jul 4, 2014 at 2:10 PM, DuyHai Doan wrote:
> c. operational simplicity due to master-less architecture. This feature
> is, although quite transparent for developers, is a key selling point.
> Having suffered when installing manually a Hadoop cluster, I happen to love
> the deployment sim
;
> Here’s a feature comparison of some NoSQL databases:
> http://kkovacs.eu/cassandra-vs-mongodb-vs-couchdb-vs-redis
>
> -- Jack Krupansky
>
> *From:* Prem Yadav
> *Sent:* Friday, July 4, 2014 10:37 AM
> *To:* user@cassandra.apache.org
> *Subject:* Cassandra use case
/datastax-opscenter
Here’s a feature comparison of some NoSQL databases:
http://kkovacs.eu/cassandra-vs-mongodb-vs-couchdb-vs-redis
-- Jack Krupansky
From: Prem Yadav
Sent: Friday, July 4, 2014 10:37 AM
To: user@cassandra.apache.org
Subject: Cassandra use cases/Strengths/Weakness
Hi,
I have seen
Duy,
if you are not already working for Datastax, they should hire you. :)
Great response. You have given me some good points to think about. I will
do the rest of the research.
Thanks.
On Fri, Jul 4, 2014 at 10:10 PM, DuyHai Doan wrote:
> I would answer your question this way:
>
> 1) Why
I would answer your question this way:
1) Why should I choose C* ?
a. linear scalability, throughputs scale "almost" linearly with number of
nodes
b. almost unbounded extensivity (there is no limit, or at least huge
limit in term of number of nodes you can have on a cluster)
c. operational
Jens,
thanks for the response but your reply doesn't serve any purpose. I asked
about use cases suitable for Cassandra. It is a basic question about what
purpose does this technology serve? My use case or requirements do not
matter in that regard. And 'fits our requirements' is not a valid reason
a
I’ve supported a variety of different “big data” systems and most have their
own particular set of use cases that make sense. Having said that, I believe
that Cassandra uniquely excels at the following:
* Low write latency with respect to small to medium write sizes (logs, sensor
data, etc.)
*
Hi,
I think you are asking the wrong first question. You should start with "What
are my requirements?". If you are only storing two items that are rarely ever
modified, any database is a good approach. We have no idea what your use case
is. We could speculate about it, but really it all boils
Thanks Manoj. Great post for those who already have Cassandra in production.
However it brings me back to my original post.
All the points you have mentioned apply to any big data technology.
Storage- All of them
Query- All of them. In fact lot of them perform better. Agree that CQL
structure is be
These are my personal opinions based on few months using Cassandra. These
are my views. Others
may have different opinion
http://khangaonkar.blogspot.com/2014/06/apache-cassandra-things-to-consider.html
regards
On Fri, Jul 4, 2014 at 7:37 AM, Prem Yadav wrote:
> Hi,
> I have seen this in a
Hi,
I have seen this in a lot of replies that Cassandra is not designed for
this and that. I don't want to sound rude, i just need some info about this
so that i can compare it to technologies like hbase, mongo,
elasticsearch, solr,
etc.
1) what is Cassandra designed for. Heave writes yes. So is H
16 matches
Mail list logo
