@David:
Like all other start-ups, we too cannot start with all dedicated servers
for Cassandra. So right now we have no better choice except for using a VPS
:), but we can definitely choose one from amongst a suitable set of VPS
configurations. As of now since we are starting out, could we initiate
I've run several lab configurations on linodes; I wouldn't run cassandra on any
shared virtual platform for large-scale production, just because your IO
performance is going to be really hard to predict. Lots of people do, though
-- depends on your cassandra loads and how consistent you need to
I am building a cluster(initially starting with a 2-3 nodes cluster). I
have came across two seemingly good options for hosting, Linode & Digital
Ocean. VPS configuration for both listed below:
Linode:-
--
XEN Virtualization
2 GB RAM
8 cores CPU (2x priority) (8 processor Xen inst
I"m referring to the core driver from datastax:
https://github.com/datastax/java-driver
You should be able to build it with maven.
Andy
On 3 Aug 2013, at 16:35, Jan Algermissen wrote:
> Hi Andrew,
>
> On 03.08.2013, at 14:30, Andrew Cobley wrote:
>
>> I've used most of the java drivers under
Keith,
On 03.08.2013, at 17:17, Keith Wright wrote:
> I definitely recommend the datastax driver so long as you plan on using cql3.
>
No, I can live with lower level querying. What I am concerned with is that
thread pool issues in JavaEE should be left to the container and I am trying to
Tony,
On 03.08.2013, at 16:36, Tony Anecito wrote:
> I use the DataStax driver anm happy with it so far.
Thanks. Also the question: are you talking about
https://github.com/datastax/java-driver or cassandra-jdbc?
Jan
> Also, think about if driver is being worked on as Cassandra gets updat
Hi Andrew,
On 03.08.2013, at 14:30, Andrew Cobley wrote:
> I've used most of the java drivers under Glashfish without a problem. IMHO
> it's really down to the functionality you require in your application. The
> Java Driver form datastax has the lowest learning curve for any java
> progra
I definitely recommend the datastax driver so long as you plan on using cql3.
Its binary protocol allows multiplexing, is vnode token aware, and does not
require serialize/deserialize to thrift. We used astyanax before and it did
work well and has support (aka recipes) for standard usage cases
I use the DataStax driver anm happy with it so far. Also, think about if driver
is being worked on as Cassandra gets updated since CQL version always getting
improved so driver needs to improve wth it. So if driver developers not work on
it often then you should not use it. Also, I think DataSta
I've used most of the java drivers under Glashfish without a problem. IMHO
it's really down to the functionality you require in your application. The
Java Driver form datastax has the lowest learning curve for any java
programmer familiar with JDBC and I believe deals with pool management.
J
Hi,
I plan on using Cassandra in a Java EE7 (Glassfish) project and I wonder which
driver I should pick.
Can anyone make a recommendation which of the available drivers fits best into
a Java EE environment?
(I looking for avoiding thread pool management issues mostly. I am not so
interested i
11 matches
Mail list logo
