cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Durity, Sean R" <>
Subject RE: [EXTERNAL] performance
Date Mon, 02 Dec 2019 15:14:59 GMT
I’m not sure this is the fully correct question to ask. The size of the data will matter.
The importance of high availability matters. Performance can be tuned by taking advantage
of Cassandra’s design strengths. In general, you should not be doing queries with a where
clause on non-key columns. Secondary indexes are not what you would expect from a relational
background (and should normally be avoided).

In short, choose Cassandra if you need high-availability and low latency on KNOWN access patterns
(on which you base your table design).

If you want an opinion – I would never put data over a few hundred GB that I care about
into mysql. I don’t like the engine, the history, the company, or anything about it. But
that’s just my opinion. I know many companies have successfully used mysql.

Sean Durity

From: hahaha sc <>
Sent: Friday, November 29, 2019 3:27 AM
To: cassandra-user <>
Subject: [EXTERNAL] performance

Query based on a field with a non-primary key and a secondary index, and then update based
on the primary key. Can it be  more efficient than mysql?


The information in this Internet Email is confidential and may be legally privileged. It is
intended solely for the addressee. Access to this Email by anyone else is unauthorized. If
you are not the intended recipient, any disclosure, copying, distribution or any action taken
or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed
to our clients any opinions or advice contained in this Email are subject to the terms and
conditions expressed in any applicable governing The Home Depot terms of business or client
engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy
and content of this attachment and for any damages or losses arising from any inaccuracies,
errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature,
which may be contained in this attachment and shall not be liable for direct, indirect, consequential
or special damages in connection with this e-mail message or its attachment.
View raw message