Over the years, I learned the hard way that, with the exception of a few niche use cases, NoSQL databases such as AWS DynamoDB or Apache Cassandra are not always a good idea.
Tag: nosql
Let’s talk cloud neutrality
Avoiding managed services, using Docker and running eight Mongo and twelve Kafka nodes does not make an application cloud neutral — it makes it costly to develop, Kafkaesque to architect, and impossible to maintain in production. You end up losing your weekends and quality time with family to DR exercises and production support.
Operations costs are the Achille’s heel of NoSQL
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.
Ten Questions to Consider Before Choosing Cassandra
1. Do you know what your queries will look like ? In traditional SQL you design your data model … More
Ordered Sets and Logs in Cassandra vs SQL
I’ve written before that Cassandra’s achilles’ heel is devops: Storage, redundancy and performance are expanded by adding more nodes. This … More
Cassandra: Lessons Learned
After using Cassandra for 3 years since version 0.8.5, I thought I’d put together a blurb on lessons learned. Here … More
Things I wish Apache Cassandra was better at
At first I wanted to name this article “My personal list of grievances against Apache Cassandra”, but I decided to … More
The Dulin Report 