4 ms·
But last year, CouchDB was the future. Today it's Cassandra. In a few months, it could well be MongoDB or Redis. Even if Cassandra ends up the NoSQL winner,
by justinsb 17y ago
But last year, CouchDB was the future. Today it's Cassandra. In a few months, it could well be MongoDB or Redis. Even if Cassandra ends up the NoSQL winner, I'm pointing out that you'll have your hands full dealing with 'must have' feature contributions from the 'losing' NoSQL store users, and that this will be painful for existing Cassandra users.
As for the Drizzle thing, you've crossed the line into misleading marketing there. There is a plugin to integrate Cassandra as a Drizzle engine, just like there's a plug-in that logs MySQL error messages to Twitter. That doesn't make it the official strategy, nor does it automatically make it a good idea.
(Edit: fixed my MongoDB/CouchDB confusion!)
- jbellis 17y ago"But last year, CouchDB was the future. Today it's Cassandra. In a few months, it could well be MongoDB or Redis." There's a reason you didn't see Twitter switching to CouchDB last year, and the reason is Cassandra is the only one of those four that does scale-out. So... no, "one of these things is not like the others." "That doesn't make it the official strategy" It makes it their only strategy at all to make it past the vapor stage. I'm not a Drizzle expert, but I do work with the core Drizzle team.