Cassandra at Scale: The Problem with Secondary Indexes | Pantheon
Maybe you're a seasoned Cassandra veteran, or maybe you're someone who's stepping out into the world of NoSQL for the first time—and Cassandra is your first step. Maybe you're well versed in the problems that secondary indexes pose, or maybe you're looking for best practices before you invest too much time and effort into including Cassandra in your stack. The truth is, if you're using Cassandra or planning on using it to retrieve data efficiently, there are some limits and caveats of indexes you should be aware of.
Here at Pantheon, we like to push things to their limits. Whether it's packing thousands of containers onto a single machine, or optimizing our PHP internals to serve up the fastest WordPress sites on the internet, we put our stack under intense pressure. Sometimes that yields diamonds, and other times that yields cracks and breakages. This article is about the latter situation—how we reached the limit of Cassandra's secondary indexes, and what we did about it. But first, some background.
Read full article from Cassandra at Scale: The Problem with Secondary Indexes | Pantheon
No comments:
Post a Comment