On Wed, Aug 17, 2016 at 2:08 PM, Tyler Hobbs wrote:
> In the spirit of the recent thread about discussing large changes on the
> Dev ML, I'd like to talk about CASSANDRA-10993, the first step in the
> "thread per core" work.
I'm just lurking ATM; I don't have anything to add WRT
CASSANDRA-10993,
>From my perspective, one of the most important reasons for RxJava would be
the strategic option to integrate reactive streams [1] in the overall
Cassandra architecture at some point in the future. Reactive streams would
allow to design back pressure fundamentally different compared to what we
do i
I think I outlined the tradeoffs I see between the roll our own vs use a
reactive framework in
https://issues.apache.org/jira/plugins/servlet/mobile#issue/CASSANDRA-10528
My view is we should try to utilize the existing before we start writing
our own. And even if we do write our own keep it react
In the spirit of the recent thread about discussing large changes on the
Dev ML, I'd like to talk about CASSANDRA-10993, the first step in the
"thread per core" work.
The goal of 10993 is to transform the read and write paths into an
event-driven model powered by event loops. This means that each
