Hi good question. The scalability of Pelops is dependent on Cassandra, not the library itself. The library aims to provide an more effective access layer on top of the Thrift API.
The library does perform connection pooling, and you can control the size of the pool and other parameters using a policy object. But connection pooling itself does not increase scalability, only efficiency. Hope this helps. BEst, Dominic On 11 June 2010 14:47, Ian Soboroff <isobor...@gmail.com> wrote: > Sounds nice. Can you say something about the scales at which you've used > this library? Both write and read load? Size of clusters and size of data? > > Ian > > > On Fri, Jun 11, 2010 at 9:41 AM, Dominic Williams < > thedwilli...@googlemail.com> wrote: > >> Pelops is a new high quality Java client library for Cassandra. >> >> It has a design that: >> * reveals the full power of Cassandra through an elegant "Mutator and >> Selector" paradigm >> * generates better, cleaner, less bug prone code >> * reduces the learning curve for new users >> * drives rapid application development >> * encapsulates advanced pooling algorithms >> >> An article introducing Pelops can be found at >> >> http://ria101.wordpress.com/2010/06/11/pelops-the-beautiful-cassandra-database-client-for-java/ >> >> Thanks for reading. >> Best, Dominic >> > >
