cassandra - Thrift, CQL3 or what? -
recently noticed cassandra , datastax pushing cql3 more. new java driver released, 1 not use thrift @ all. , if not going use "compact storage" not able use thrift application. thus, believe thrift fading out cassandra.
my question is, new application should go head , use cql3? however, still prefer thrift because want know what's going on underneath , on other hand not want using fading out , becoming legacy. recommend?
my company went through same thought process , ended using cql3 on thrift.
although there slight lack of transparency additional layer of abstraction going on cql3, ease , familiarity of writing sql style statements makes code more readable , intuitive in opinion. plus found cqlsh interface far more user friendly cassandra-cli debugging , general db maintenance (the auto-complete fab in cqlsh!).
once understand underlying data structure , how cql3 represents data, layer of abstraction pales insignificance, really.
Comments
Post a Comment