Re: Requesting some details for my use case

2016-01-07 Thread Bhuvan Rawal
Hi Jack, We are valuing reliability and consistency over performance right now. In E-commerce industry we can expect unexpected spikes at odd times. Ill be grateful if you tell me about reliability and failover scenarios. On Wed, Jan 6, 2016 at 2:59 AM, Jack Krupansky wrote: > DataStax has doc

Re: Requesting some details for my use case

2016-01-05 Thread Jack Krupansky
DataStax has documented quite a few customers/case studies: http://www.datastax.com/resources/casestudies Materialized Views should be considered if you can go straight to 3.0, but you can always do the same synthesized views yourself in your app, which is current standard best practice anyways. M

Re: Requesting some details for my use case

2016-01-05 Thread Bhuvan Rawal
Thanks for pointing out the typo Jonathan. Our use case is of Column Family. :) On Wed, Jan 6, 2016 at 2:38 AM, Jonathan Haddad wrote: > Sorry to nitpick, but Cassandra is not a columnar database. If you're > looking for columnar because you have an analytics need, Cassandra is not > what you w

Re: Requesting some details for my use case

2016-01-05 Thread Jonathan Haddad
Sorry to nitpick, but Cassandra is not a columnar database. If you're looking for columnar because you have an analytics need, Cassandra is not what you want. If you've just made the same mistake that 99% of people make, well, now you know. Cassandra historically has been referred to as a "Colum

Re: Requesting some details for my use case

2016-01-05 Thread Bhuvan Rawal
*Thanks Jack* *for the detailed advice*. Yes it is a Java Application. We have a Denormalized view of our data already in place, we use it for storing it in MongoDB as a cache, however will get our hands dirty before implementation. We would like to have a single DB view. And replace MongoDB & M

Re: Requesting some details for my use case

2016-01-05 Thread Jack Krupansky
Bear in mind that you won't be able to merely "tune" your schema - you will need to completely redesign your data model. Step one is to look at all of the queries you need to perform and get a handle on what flat, denormalized data model they will need to execute performantly in a NoSQL database. N

Re: Requesting some details for my use case

2016-01-05 Thread Bhuvan Rawal
I understand, Ravi, we have our application layers well defined. The major changes will be in database access layers and entities will be changed. Schema will be modified to tune the efficiency of the data store chosen. We have been using mongo as a cache for a long time now, but as its a documen

Re: Requesting some details for my use case

2016-01-05 Thread Ravi Krishna
You are moving from a SQL database to C* ??? I hope you are aware of the differences between a nosql like C* and a RDBMS. To keep it short, the app has to change significantly. Please read documentation on differences between nosql and RDBMS. thanks. On Tue, Jan 5, 2016 at 6:20 AM, Bhuvan Rawal

Requesting some details for my use case

2016-01-05 Thread Bhuvan Rawal
Hi All, Im planning to shift from SQL database to a columnar nosql database, we have streamlined our choices to Cassandra and HBase. I would really appreciate if someone decent experience with both give me a honest comparison on below parameters (links to neutral benchmarks/blogs also appreciated)