- How it compares to Cassandra regarding latency?
- How is the client API? Does it support lock free communication? Can you send things to nodes in batches?
this seems like an ad for cassandra, many comments on how it scales and how partitioning is easy but no concrete examples at all. Having used cassandra in the past, it sure isn't the holy grail of nosql dbs, especially not for analytics that this article suggests
Thanks, I forgot about the NoSQL part due to tunable consistency.
I remembered Cassandra as almost similar to SQL databases with horizontal scalability.
I read that more as what he normally uses for tests and demos since it can be really easily generated using native SQL functions, and not necessarily his day job. Not that it matters much, I guess, and I agree it'd be neat to see that compared to Cassandra.
We just did a benchmarking for a PoC on DocumentDB side-by-side Cassandra. It does the job, I have not yet seen anything revolutionary. Cassandra benchmarks seemed better.
How will we add new machines?
Are their any single points of failure?
Do the writes scale as well?
How much administration will the system require?
If its open source, is there a healthy community?
(And I would add, is it _fast_ as well as scalable?)
We had a sales call with them last year and got to speak to one of their devs. The impression they gave was that it was mostly ex-Facebook data guys that left to start a company based on the work they did on Cassandra and a few other internal projects.
The really interesting feature, to us, was the promise that once the Postgres-compatible layer was complete, we could use whatever semantics were appropriate for our business use case while using the same logical database cluster. We could use the Redis interface for persistent caching, the CQL interface for our NoSQL-appropriate use cases and the Postgres interface for our more traditional use cases. And the client libraries for all those interfaces are the same ones we already use to talk to Redis and Postgres (our conversation happened because we were starting a project that was more NoSQL-appropriate, so we weren’t using Cassandra yet), so very little of our code would have to change.
For awhile, all the buzz about the future of databases was NoSQL systems. I recall hearing for awhile about how great Cassandra was and that Cassandra was basically an open-source equivalent to Google's BigTable. Everything I've read seems to indicate that Cassandra may be more trouble than its worth ( http://en.wikipedia.org/wiki/Apache_Cassandra#Prominent_users ).
Who here has actually used Cassandra DB? Are you happy with it? Is there a better alternative if I'm concerning moving away from MySQL?
"While in theory, NoSQL databases can be deployed on hundreds or thousands of
machines, in practice the deployments are much smaller and can typically easily fit within a
single Oracle database with fewer and more reliable components. The largest production
Cassandra cluster has over 100 TB of data in over 150 machines."
I find this interesting. I wonder if there any real TCO comparisons have been done to this point.
Sure, this paper is full of FUD. But it does raise a valid question for me: What's the difference between paying for Oracle and paying for MySQL, Datastax, or Cloudera support/enterprise to get the added features needed to run my business and keep away from reinventing the wheel?
reply