October 10, 2016 | Cassandra
In the culmination of our blog series on the topic, on October 6th 2016 OpenCredo Consultants Dominic Fox, Alla Babkina and Guy Richardson, and hosted by Marco Cullen, presented the common design and implementation issues that they have come across in real-world Apache Cassandra deployments.
If you missed the webcast or would like to watch it again, here is a recording.
Fulfilling the promise of Apache Cassandra performance By Guy Richardson
Like all technologies, Cassandra operates according to certain principles and conventions. These conventions enable Cassandra to yield outstanding performance and support complex data needs, but this comes at the expense of some fundamental limitations. You should assess and understand these limitations before committing to Cassandra as a technology, and align your rollout of Cassandra with this understanding to ensure that future performance and ongoing operations are within your expected bounds.
Patterns of Successful Cassandra Data Modelling By Alla Babkina
A growing number of clients are asking OpenCredo for help with using Apache Cassandra and solving specific problems they encounter. Clients have different use cases, requirements, implementation and teams but their similar issues. We have noticed that Cassandra data modelling problems are the most consistent cause of Cassandra failing to meet their expectations. Data modelling is one of the most complex areas of using Cassandra and has many considerations
How Not To Use Cassandra Like An RDBMS (and what will happen if you do) By Dominic Fox
Cassandra isn’t a relational database management system, but it has some features that make it look a bit like one. In this post, Dominic reviews a few example scenarios where a beginner might be unpleasantly surprised by the differences, and suggests some remedies.
Common Problems with Cassandra Tombstones By Alla Babkina
Cassandra is optimised for writes and everything, including logical deletion of data, results in extra records being inserted. Every deletion in Cassandra results in a tombstone, a record marking deletion. We have noticed that lack of understanding of tombstones is often the root cause of production issues our clients experience with Cassandra. We have decided to share a compilation of the most common problems with Cassandra tombstones and some practical advice on solving them.
This blog is written exclusively by the OpenCredo team. We do not accept external contributions.
Decision time with AWS KeyspacesWith the upcoming Cassandra 4.0 release, there is a lot to look forward to. Most excitingly, and following a refreshing realignment of the Open Source…
Riak, the Dynamo paper and life beyond BashoRecently, the sad news has emerged that Basho, which developed the Riak distributed database, has gone into receivership. This would appear to present a problem…