Hi Oliver,
I was in a similar situation to you and Matija a few years back as well and
can vouch for what Matija has said. Some data sets are more suitable for
Cassandra than others; so the answer to your question depends on the type
of data and how it is modelled in Cassandra. The data model will
THERE ARE NO JOINS WITH CASSANDRA
CQL != SQL
Same for aggregation, subqueries, etc. And effectively multitable
transactions are out.
If you have simple single-table queries and updates, or can convert the app
to do so, then you're in business.
On Tue, Mar 13, 2018 at 5:02 AM, Rahul Singh
wrote
Oliver,
Here’s the criteria I have for you:
1. Do you need massive concurrency on reads and writes ?
If not you can replicate MySQL using master slave. Or consider Galera - Maria
DB master master. I’ve not used it but then again doesn’t mean that it doesn’t
work. If you have time to experimen
Cassandra is going to be die in next few time (What I see) - Cassandra
is not solving the purpose rather people are facing fewer issue
sometime where in virtual environments.
We have tried crdb database cluster and migrated few of cluster over
on the cockroach database environment, it seems workin
Hi Oliver,
Few years back I had a similar problem where there was a lot of data in
MySQL and it was starting to choke. I migrated data to Cassandra, ran
benchmarks and blew MySQL out of the water with a small 3 node C* cluster.
If you have a use case for Cassandra the answer is yes, but keep in mi
Hi,
On Mon, Mar 12, 2018 at 8:58 PM Oliver Ruebenacker wrote:
> We have a project currently using MySQL single-node with 5-6TB of data and
> some performance issues, and we plan to add data up to a total size of
> maybe 25-30TB.
>
There is no 'silver bullet', the Cassandra is not a 'drop in' re
