Hi, I've been running a number of tests with Cassandra using a couple of PHP drivers (namely PHPCassa (https://github.com/thobbs/phpcassa/) and PDO-cassandra (http://code.google.com/a/apache-extras.org/p/cassandra-pdo/), and the experience hasn't been great, mainly because I can't try out the CQL3.
Aaron Morton (aa...@thelastpickle.com) advised: "If possible i would avoid using PHP. The PHP story with cassandra has not been great in the past. There is little love for it, so it takes a while for work changes to get in the client drivers. AFAIK it lacks server side states which makes connection pooling impossible. You should not pool cassandra connections in something like HAProxy." So my question is - if you were to build a new scalable project from scratch tomorrow sitting on top of Cassandra, which technologies would you select to serve HTTP requests to ensure you get: a) The best support from the cassandra community (e.g. timely updates of drivers, better stability) b) Optimal efficiency between webservers and cassandra cluster, in terms of the performance of individual requests and in the volumes of connections handled per second c) Ease of development and and deployment. What worked for you, and why? What didn't work for you? Thanks, Andy -- Andy Ballingall Senior Software Engineer The Foundry 6th Floor, The Communications Building, 48, Leicester Square, London, WC2H 7LT, UK Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 Web: http://www.thefoundry.co.uk/ The Foundry Visionmongers Ltd. Registered in England and Wales No: 4642027
