Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evaluate Cassandra as storage backend #101

Open
krasserm opened this issue May 15, 2013 · 3 comments
Open

Evaluate Cassandra as storage backend #101

krasserm opened this issue May 15, 2013 · 3 comments
Assignees
Labels

Comments

@krasserm
Copy link
Contributor

Criteria:

  • Load distribution
  • Read consistency
  • ...
@ghost ghost assigned krasserm May 15, 2013
@ahjohannessen
Copy link
Contributor

👍

@javierarrieta
Copy link

Managing queues with cassandra is a known antipattern because of how cassandra marks deletes as tombstones and navigating through the queu will have to scan the previous tombstones to fetch the next slice

http://www.datastax.com/dev/blog/cassandra-anti-patterns-queues-and-queue-like-datasets

@javierarrieta
Copy link

Having said that astyanax has a recipe to write durable queues to Cassandra, could be interesting finding if it is possible to convert that to CQL and if it is not affected by the tombstone issue

https://github.com/Netflix/astyanax/wiki/Message-Queue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants