cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bhuvan Rawal <bhu1ra...@gmail.com>
Subject Re: Requesting some details for my use case
Date Tue, 05 Jan 2016 15:52:14 GMT
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
document store and since we have a crisp well defined schema we chose to go
with a columnar database.

Our data size has been growing very rapidly. Currently it is 200GB with
indexes, in couple of years it will grow up to approx 5 TB. And we may need
to run procedures to aggregate data and update tables.

On Tue, Jan 5, 2016 at 6:54 PM, Ravi Krishna <sravikrishna3@gmail.com>
wrote:

> 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 <bhu1rawal@gmail.com> wrote:
>
>> 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):
>>
>> 1. Data Consistency (Eventual consistency allowed but define "eventual")
>> 2. Ease of Scaling Up
>> 3. Managebility
>> 4. Failure Recovery options
>> 5. Secondary Indexing
>> 6. Data Aggregation
>> 7. Query Language (3rd party wrapper solutions also allowed)
>> 8. Security
>> 9. *Commercial Support for quick solutions to issues*.
>> 10. Run batch job on data like map reduce or some common aggregation
>> functions using row scan. Any other packages for cassandra to achieve this?
>> 11. Trigger specific updates on tables used for secondary index.
>> 12. Please consider that our DB will be the source of truth, with no
>> specific requirement of immediate data consistency amongst nodes.
>>
>> Regards,
>> Bhuvan Rawal
>> SDE
>>
>
>

Mime
View raw message