cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian O'Neill <boneil...@gmail.com>
Subject Re: Any reason to limit one's self to a single high level java client?
Date Mon, 02 Jul 2012 14:44:35 GMT
The only trouble you might run into is classpath conflicts, but as long as
they are using compatible versions of common dependencies you should be
okay.

-brian

-- 
Brian O'Neill
Lead Architect, Software Development
Health Market Science | 2700 Horizon Drive | King of Prussia, PA 19406
p: 215.588.6024
www.healthmarketscience.com

From:  David Leimbach <leimy2k@gmail.com>
Reply-To:  <user@cassandra.apache.org>
Date:  Mon, 2 Jul 2012 07:34:34 -0700
To:  user <user@cassandra.apache.org>
Subject:  Any reason to limit one's self to a single high level java client?

I recognize that behind the scenes there's connection pooling and all kinds
of nice asynchronous dispatch of requests to cassandra, but is there any
sort of reason to avoid using different Java clients in the same
application?

I'm noticing that some are better suited to certain kinds activity than
others.

Dave



Mime
View raw message