One or two keyspaces in Cassandra for a different kind of data of the single application -

One or two keyspaces in Cassandra for a different kind of data of the single application -

in project utilize cassandra analytics , mysql store data. see cassandra fit info well.

my question is: should create new keyspace info or should utilize keyspace exists used analytical data? should take business relationship when making such decision?

my stack python (django) + pycassa, cassandra 1.2.

keyspace high level grouping of similar column families. there no hard , fast rules, , important implications of either decision relate specific client library's api. personally, create new keyspace when want separation of concerns data. it's analogous creating different database in relational db.

cassandra