cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Major <al3...@gmail.com>
Subject Re: What is the ideal server-side technology stack to use with Cassandra?
Date Mon, 20 Aug 2012 12:42:21 GMT
On Sun, Aug 19, 2012 at 11:04 PM, Tyler Hobbs <tyler@datastax.com> wrote:

> On Sun, Aug 19, 2012 at 3:55 AM, aaron morton <aaron@thelastpickle.com>wrote:
>
>>
>>
>> It is not a judgement on the quality of PHPCassa or PDO-cassandra,
>> neither of which I have used.
>>
>> My comments were mostly informed by past issues with Thrift and PHP.
>>
>
> Eh, you don't need to disclaim your opinion that much :)
>
> The PHP clients have, overall, been a bit rough and slow moving compared
> to the Java and Python clients.  My hope is that the transition to cql3
> will it easier to maintain the drivers and clients; it just tends to be a
> lot of work with PHP.
>
> Thrift does have some issues of its own, so perhaps the custom protocol
> that's replacing it will smooth out some of the issues.  Regardless, some
> work on enabling persistent connections is definitely needed.  If anybody
> is familiar enough with that to lend a hand, I would be glad to get some
> kind of support in.
>
> --
> Tyler Hobbs
> DataStax <http://datastax.com/>
>
>
The company I work for currently uses PHP with Cassandra in production and
we're certainly interested in helping out with this. However for persistent
connections and some of the more advanced features, I think it would
require a move away from PHPCassa to the PDO extension. I was around when
the mysql extension introduced persistent connections and it wasn't as
painful as first thought.

We're using PHPCassa at the moment, but currently doing a data-model
re-write towards CQL3 with compound columns/sets. For our part, we were
looking at first moving the PDO driver (which needs some TLC) to CQL3, but
not until the native driver is out in Cassandra 1.2.

The only thing that the PHP Driver won't natively be able to handle
properly is connection pooling (as its stateless), however that can fairly
painlessly be handled in the application via APC (we currently use this
option).

Given a little time I would have confidence that PHP drivers will catch up
to other language drivers, I know we're not the only ones interested in
helping out with that effort.

Mime
View raw message