Another option may be virtual column families with PlayOrm. We currently
do around 60,000 column families to store data from 60,000 different
sensors that keep feeding us information.
Dean
On 5/6/13 11:18 AM, "Robert Coli" wrote:
>On Sun, May 5, 2013 at 11:37 PM, Darren Smythe
>wrote:
>> How
On Sun, May 5, 2013 at 11:37 PM, Darren Smythe wrote:
> How many keyspaces can you reasonably have?
"Very Low Hundreds", though this relates more to CFs than Ks.
> If we have 1000 customers, so one KS per customer is 1000 keyspaces. Is that
> something C* can handle efficiently?
No.
> I guess
You may want to look at using virtual keyspaces:
http://hector-client.github.io/hector/build/html/content/virtual_keyspaces.html
And follow these tickets:
http://wiki.apache.org/cassandra/MultiTenant
-brian
On May 6, 2013, at 2:37 AM, Darren Smythe wrote:
> How many keyspaces can you reasonab
How many keyspaces can you reasonably have? We have around 500 customers
and expect that to double end of year. We're looking into C* and wondering
if it makes sense for a separate KS per customer?
If we have 1000 customers, so one KS per customer is 1000 keyspaces. Is
that something C* can handle
