Hey,

I am looking ideas/best practices on an invoice, contact info,
notes, CRM type database which keeps every change ever made permanently. I
have some ideas on how to build this but I don't have any idea what best
practice is on partitioning the families of data.

I can do column families
for contact info, invoices, notes etc. - but that may be several column
families and the docs suggests a max of 2. If I could get some tips on that
it'd be appreciated.

Best, James

Reply via email to