Definitely not weekend, I thought about a year of hard development. I
went throw Cassandra code, and can see a lot of work.
------ Original Message ------
From: "Michael Kjellman" <mkjell...@barracuda.com>
To: "dev@cassandra.apache.org" <dev@cassandra.apache.org>; "Roman
Vasilyev" <rvasil...@netflix.com>
Cc: "Brandon Williams" <dri...@gmail.com>
Sent: 12/19/2013 11:38:54 AM
Subject: Re: Re[2]: C* engine
You seem to think something like this is akin to a weekend project. I
would recommend you actually read some of the Cassandra source code and
better understand how it is architected.
On Dec 19, 2013, at 11:30 AM, "Roman Vasilyev"
<rvasil...@netflix.com> wrote:
I'm not talking to throw away currently working code. Just port it to
C/C++, and have option to run Java based or "native" binary.
------ Original Message ------
From: "Brandon Williams" <dri...@gmail.com>
To: dev@cassandra.apache.org; "Roman Vasilyev"
<rvasil...@netflix.com>
Sent: 12/19/2013 11:26:21 AM
Subject: Re: C* engine
Let's ask what we'll lose here.
4 years of work, tons of debugging, loads of instrumentation, for
what
gain? Almost nil.
On Thu, Dec 19, 2013 at 1:22 PM, Roman Vasilyev
<rvasil...@netflix.com>
wrote:
Hello,
Don't want to rise "holy war". Just let me share my crazy thoughts.
I believe it could improve Cassandra speed and robustness.
What people will say if I propose to have Cassandra engine written
in
C/C++, and this engine will give you ability to run extensions in
Java, Groovy and bunch other languages like Perl/Python/Ruby?
I just want to understand for myself does this solution will be
useful
or I'm looking in wrong direction?
Thank you for reading.
===========================================================
Find out how eSigning generates significant financial benefit.
Read the Barracuda SignNow ROI whitepaper at
https://signnow.com/l/business/esignature_roi
