Re: data agility

From: Milind Parikh To: user@cassandra.apache.org Sent: Sunday, 20 November 2011, 22:51 Subject: Re: data agility For 99% of current applications requiing a persistent datastore, Oracle, PgSQL and MySQL variants will suffice.   For the 1% of the applicat

Re: data agility

For 99% of current applications requiing a persistent datastore, Oracle, PgSQL and MySQL variants will suffice. For the 1% of the applications, consider C* if (a) you have given up on distributed transactions ("ACID"LY; but NOT "BASE"ICLY) (b) wondering about this new fangled ho

Re: data agility

Thanks Aaron, I kept this use-case free as to focus on the higher level description, it might have been a not a good idea. But generally I think I got a better intuition from the various answers, thanks! -- Dotan, @jondot On Sun, Nov 20, 2011 at 11:52 PM, Aaron Turn

Re: data agility

Sounds like you need to figure out what your product is going to do and what technology will best fit those requirements. I know you're worried about being agile and all that, but scaling requires you to use the right tool for the job. Worry about new requirements when they rear their ugly head ra

Re: data agility

Jahangir, thanks! however I've noted that we may very well need to scale to 200M users or "entities" within a short amount of time - say a year or two, 10M within few months. -- Dotan, @jondot On Sun, Nov 20, 2011 at 11:14 PM, Jahangir Mohammed wrote: > IMHO, you

Re: data agility

IMHO, you should start with something very simple RDBMS and meanwhile getting handle over Cassandra or other noSql technology. Start out with simple, but always be aware and conscious of the next thing you will have in stack. It's timetaking to work with new technology if you are in the phase of pr

Re: data agility

Thanks David. Stephen: thanks for the tip, we can run a recommended configuration, so that wouldn't be an issue. I guess I can focus that my questions are on complexity of development. After digesting David's answer, I guess my follow up questions would be - how would you process data in a cassand

Re: data agility

if your startup is bootstrapping then cassandra is sometimes to heavy to start with. i.e. it needs to be fed ram... you're not going to seriously run it in less than 1gb per node... that level of ram commitment can be too much while bootstrapping. if your startup has enough cash to pay for 3-5 re

Re: data agility

Dotan, I think that if you're in the early stages you have a basic idea of what your product is going to be, architecturally speaking. While you may change your business model, or features at the display layer, I would think the data models itself would remain relatively similar throughout...othe

data agility

Hi all, my question may be more philosophical than related technically to Cassandra, but please bear with me. Given that a young startup may not know its product full at the early stages, but that it definitely points to ~200M users, would Cassandra will be the right way to go? That is, the requi