IME/O one of the best things about Cassandra was the separation of (and I'm
over-simplifying a bit, but still):
- The transport/API layer
- The Datacenter layer
- The Storage layer
> I don't think we're well-served by the "construction kit" approach.
> It's difficult enough to evaluate NoSQL without deciding if you should
> run CQLSandra or Hectorsandra or Intravertandra etc.
In tree, or even documented, I agree completely. I've never argued CQL3 is
not the best approach for new users.
But I've been around long enough that I know precisely what I want to do
sometimes and any general purpose API will get in the way of that.
I would like the transport/API layer to at least remain pluggable
("hackable" if you will) in it's current form. I really just want to be
able to create my own *Daemon - as I can now - and go on my merry way
without having to modify any internals. Much like with compaction
strategies and SSTable components.
Do you intend to change this current behavior of allowing a custom
transport without code modification? (as opposed to changing the daemon
class in a script?).
