giving some credit to eric flo
This commit is contained in:
parent
d4f400855f
commit
704c181145
@ -7,6 +7,8 @@ The advantage to using this over other solutions is that your data is persistent
|
|||||||
unlike memcached, and Cassandra is designed to store key-value data like
|
unlike memcached, and Cassandra is designed to store key-value data like
|
||||||
this, so performance is much closer to that of memcached than with a database.
|
this, so performance is much closer to that of memcached than with a database.
|
||||||
|
|
||||||
|
Note: This work was initially based off of [tokyo-tyrant-sessions](http://github.com/ericflo/django-tokyo-sessions) by Eric Flo.
|
||||||
|
|
||||||
Installing cassandra-sessions
|
Installing cassandra-sessions
|
||||||
-----------------------------
|
-----------------------------
|
||||||
|
|
||||||
@ -33,6 +35,3 @@ Installing cassandra-sessions
|
|||||||
<ReplicationFactor>1</ReplicationFactor>
|
<ReplicationFactor>1</ReplicationFactor>
|
||||||
<EndPointSnitch>org.apache.cassandra.locator.EndPointSnitch</EndPointSnitch>
|
<EndPointSnitch>org.apache.cassandra.locator.EndPointSnitch</EndPointSnitch>
|
||||||
</Keyspace>
|
</Keyspace>
|
||||||
|
|
||||||
That's it. Hopefully this backend gives you all the better performance while
|
|
||||||
still not sacrificing persistence.
|
|
Reference in New Issue
Block a user