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" <rc...@eventbrite.com> wrote: >On Sun, May 5, 2013 at 11:37 PM, Darren Smythe <darren1...@gmail.com> >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 the same question applies to our notion of breaking up the >>column >> families into time ranges. We're naively trying to avoid having few >>large >> CFs/KSs. Is/should that be a concern? > >Very large rows are significantly worse than very large CFs or KS. > >=Rob
