About
This article is about queue in cassandra.
Queue are not well supported in cassandra because deleted items are tombstones <asynch-deletes>. Cassandra must scan past in order to read from the front of the queue. And over time read performance degrades.
The classic implementation would be:
- Each item in the queue is stored with a timestamp in a wide partition.
- Items are appended to the end of the queue and read from the front, being deleted after they are read.
Any design that relies on the deletion of data is potentially a poorly performing design.