On Aug 19, 2012 9:55 AM, "aaron morton" <aa...@thelastpickle.com> wrote: > > > 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." > > Please note, this was a personal opinion expressed off list. > > It is not a judgement on the quality of PHPCassa or PDO-cassandra, neither of which I have used.
I'd like to apologise to Aaron for taking part of a private message and sharing it in public without permission, and for any potential embarrassment caused. I'm certainly embarrassed by the thoughtlessness I've displayed. I've used PHP successfully in many projects, and though I didn't take his comment as a criticism of the efforts of others in the PHP community, I now appreciate that some might do. In any case, nothing excuses my lack of respect for Aaron's privacy, which was a victim purely of particularly clumsy attempt to open up a public debate and no more. I suspect I'm not the only person trying to identify the suitability or otherwise of an application stack with Cassandra. In general, if there's a path of least resistance, or a path supported by a larger community, then I'd consider that path rather than impose choices that worked in previous projects. As Cassandra will probably be the core of that I'm working on, if there are good reasons why PHP isn't an optimal choice, then I'd consider adopting the alternative, and that's all I'm trying to get to the bottom of. Believe me, I'd prefer not to learn yet-another-software stack if I can help it! Finally, I do hope that despite my stupidity, Aaron will forgive me and contribute to this discussion. Andy > > My comments were mostly informed by past issues with Thrift and PHP. > > Aaron > > ----------------- > Aaron Morton > Freelance Developer > @aaronmorton > http://www.thelastpickle.com > > On 17/08/2012, at 10:09 PM, Andy Ballingall TF < balling...@thefoundry.co.uk> wrote: > > > 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 >
