NoSQL databases scale by adding more commodity servers. With more commodity servers come increased costs and complexities. Some NoSQL systems are better at this than others and need less. Continue reading Operations costs are the Achille’s heel of NoSQL
1. Do you know what your queries will look like ? In traditional SQL you design your data model to represent your business objects. Your queries can then evolve over time and can be ad-hoc. You can even create views, materialized or otherwise, to facilitate even more complex analytical queries. Cassandra does not offer the flexibility of traditional SQL. While your data model can … Continue reading Ten Questions to Consider Before Choosing Cassandra
I’ve written before that Cassandra’s achilles’ heel is devops: Storage, redundancy and performance are expanded by adding more nodes. This can happen during normal business hours as long as consistency parameters are met. Same applies to node replacements. As the number of servers grows be prepared to hire a devops army or look for a managed solution. Datastax offering helps but still not enough. Even … Continue reading Ordered Sets and Logs in Cassandra vs SQL
In November last year I pointed out how tempted I was to replace Cassandra with DynamoDB. Since then I have done some research and things are not as straightforward as they may seem at first. I’d like to revisit my post and clarify a few things. On elasticity of Cassandra I said the following: Scaling a Cassandra cluster involves adding new nodes. Each additional node … Continue reading Trying to Replace Cassandra with DynamoDB ? Not so fast
I have written about Cassandra in the past. I have been using Cassandra actively for the past three years, and I am one of the big advocates of technology out there. However, as I have pointed in this blog and on my Twitter page – if you plan on scaling Cassandra out, be prepared to recruit an army of Java developers to do devops. Cassandra … Continue reading Why I am Tempted to Replace Cassandra With DynamoDB
