With fault tolerance and reliability, it also gives a faster lookup mechanism across various nodes in a cluster. Amazon's dynamo paper might be a better read to understand the reasoning behind a DHT based system: http://www.allthingsdistributed.com/files/amazon-dynamo-sosp2007.pdf
On Wed, Jun 29, 2016 at 11:48 PM, Jens Rantil <jens.ran...@tink.se> wrote: > Some reasons I can come up with: > - it would be hard to have tunable read/consistencies/replicas when > interfacing with a file system. > - data locality support would require strong coupling to the distributed > file system interface (if at all possible given that certain sstables > should live on the same data node). > - operator complexity both administering a distributed file system as well > as a Cassandra cluster. This was a personal reason why I chose Cassandra > instead of HBase for a project. > > Cheers, > Jens > > Den ons 29 juni 2016 13:01jean paul <researche...@gmail.com> skrev: > >> >> >> 2016-06-28 22:29 GMT+01:00 jean paul <researche...@gmail.com>: >> >>> Hi all, >>> >>> Please, What is the motivation for choosing a DHT ring in cassandra? Why >>> not use a normal parallel or distributed file system that supports >>> replication? >>> >>> Thank you so much for clarification. >>> >>> Kind regards. >>> >> >> -- > > Jens Rantil > Backend Developer @ Tink > > Tink AB, Wallingatan 5, 111 60 Stockholm, Sweden > For urgent matters you can reach me at +46-708-84 18 32. > -- Thanks, -Utkarsh
