Ironically, we started with an Thrift based application stack which used Mysql as it's backend storage. At some point I was introduced to Cassandra, and after a very short time we implemented it as our backend storage mechanism.
The first version of our application used the Cassandra thrift client directly, which was fine if a little muddled. We tried all the other clients be failed to see any improvement over the Cassandra Thrift client. Until the latest version of Hector was released, which we have now started to use. We've been very impressed with it, and it's currently in our production environment. In terms of bindings in use for cassandra, we use java, cocoa and php. All of which work fine. We have had to write our own framed transport for cocoa (which was very simple) so we can use our cassandra management tool (Palladium) which is written using cocoa. (BTW we will be providing Palladium as a free download in the next few months). The key thing to note, is because there are so many bindings for Cassandra you can pick the technology which suites your requirements, and not be shoe horned into using something which 'kinda' works. --Jools On 14 January 2011 17:24, Ertio Lew <ertio...@gmail.com> wrote: > Hey, > > If you have a site in production environment or considering so, what > is the client that you use to interact with Cassandra. I know that > there are several clients available out there according to the > language you use but I would love to know what clients are being used > widely in production environments and are best to work with(support > most required features for performance). > > Also preferably tell about the technology stack for your applications. > > Any suggestions, comments appreciated ? > > Thanks > Ertio >
