You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by James Pirz <ja...@gmail.com> on 2012/06/28 03:04:27 UTC
which high level Java client
Dear all,
I am interested in using Cassandra 1.1.1 in a read-intensive scenario,
where more than 95% of my operations are get().
I have a cluster with ~10 nodes, around 15-20 GB of data on each, while in
the extreme case I expect to have 20-40 concurrent clients.
I am kind of confused about which high level java client should I use ?
(Which one is the best/fastest for concurrent read operations)
Hector, Pelops, Astyanax, or something else ?
I browsed the mailing list, but I came across different types of arguments
and conclusions on behalf of various clients.
Thanks in advance,
James
Re: which high level Java client
Posted by Brian O'Neill <bo...@alumni.brown.edu>.
FWIW,
We keep most of our system level integrations behind REST using Virgil:
https://github.com/hmsonline/virgil
When a lower-level integration is necessary we use Hector, but
recently we've started using Astyanax and plan to port our Hector
dependencies over to Astyanax when given a chance.
I've also been looking to implement a Spring Data JPA adaptor like
what is available for MongoDB.
https://github.com/boneill42/spring-data-mongodb
I've forked the SpringSource Cassandra repo here if anyone wants to help out:
https://github.com/boneill42/spring-data-cassandra
-brian
On Thu, Jun 28, 2012 at 9:02 AM, Vivek Mishra <mi...@gmail.com> wrote:
>
> Would like to add one more https://github.com/impetus-opensource/Kundera . Next release is planned with many distinguishing features.
>
> -Vivek
>
>
> On Thu, Jun 28, 2012 at 6:23 PM, Sasha Dolgy <sd...@gmail.com> wrote:
>>
>> Not following this thread too much, but there is also https://github.com/Netflix/astyanax/
>>
>> "Astyanax is currently in use at Netflix. Issues generally are fixed as quickly as possbile and releases done frequently."
>>
>> -sd
>>
>> On Thu, Jun 28, 2012 at 2:39 PM, Poziombka, Wade L <wa...@intel.com> wrote:
>>>
>>> I use Pelops and have been very happy. In my opinion the interface is cleaner than that with Hector. I personally do like the serializer business.
>>>
>>> -----Original Message-----
>>> From: Radim Kolar [mailto:hsn@filez.com]
>>> Sent: Thursday, June 28, 2012 5:06 AM
>>> To: user@cassandra.apache.org
>>> Subject: Re: which high level Java client
>>>
>>> i do not have experience with other clients, only hector. But timeout management in hector is really broken. If you expect your nodes to timeout often (for example, if you are using WAN) better to try something else first.
>>
>>
>>
>>
>> --
>> Sasha Dolgy
>> sasha.dolgy@gmail.com
>
>
--
Brian ONeill
Lead Architect, Health Market Science (http://healthmarketscience.com)
mobile:215.588.6024
blog: http://weblogs.java.net/blog/boneill42/
blog: http://brianoneill.blogspot.com/
Re: which high level Java client
Posted by Vivek Mishra <mi...@gmail.com>.
Would like to add one more https://github.com/impetus-opensource/Kundera .
Next release is planned with many distinguishing features.
-Vivek
On Thu, Jun 28, 2012 at 6:23 PM, Sasha Dolgy <sd...@gmail.com> wrote:
> Not following this thread too much, but there is also
> https://github.com/Netflix/astyanax/
>
> "Astyanax is currently in use at Netflix <http://movies.netflix.com/>.
> Issues generally are fixed as quickly as possbile and releases done
> frequently."
>
> -sd
>
> On Thu, Jun 28, 2012 at 2:39 PM, Poziombka, Wade L <
> wade.l.poziombka@intel.com> wrote:
>
>> I use Pelops and have been very happy. In my opinion the interface is
>> cleaner than that with Hector. I personally do like the serializer
>> business.
>>
>> -----Original Message-----
>> From: Radim Kolar [mailto:hsn@filez.com]
>> Sent: Thursday, June 28, 2012 5:06 AM
>> To: user@cassandra.apache.org
>> Subject: Re: which high level Java client
>>
>> i do not have experience with other clients, only hector. But timeout
>> management in hector is really broken. If you expect your nodes to timeout
>> often (for example, if you are using WAN) better to try something else
>> first.
>>
>
>
>
> --
> Sasha Dolgy
> sasha.dolgy@gmail.com
>
Re: which high level Java client
Posted by Sasha Dolgy <sd...@gmail.com>.
Not following this thread too much, but there is also
https://github.com/Netflix/astyanax/
"Astyanax is currently in use at Netflix <http://movies.netflix.com/>.
Issues generally are fixed as quickly as possbile and releases done
frequently."
-sd
On Thu, Jun 28, 2012 at 2:39 PM, Poziombka, Wade L <
wade.l.poziombka@intel.com> wrote:
> I use Pelops and have been very happy. In my opinion the interface is
> cleaner than that with Hector. I personally do like the serializer
> business.
>
> -----Original Message-----
> From: Radim Kolar [mailto:hsn@filez.com]
> Sent: Thursday, June 28, 2012 5:06 AM
> To: user@cassandra.apache.org
> Subject: Re: which high level Java client
>
> i do not have experience with other clients, only hector. But timeout
> management in hector is really broken. If you expect your nodes to timeout
> often (for example, if you are using WAN) better to try something else
> first.
>
--
Sasha Dolgy
sasha.dolgy@gmail.com
RE: which high level Java client
Posted by "Poziombka, Wade L" <wa...@intel.com>.
I use Pelops and have been very happy. In my opinion the interface is cleaner than that with Hector. I personally do like the serializer business.
-----Original Message-----
From: Radim Kolar [mailto:hsn@filez.com]
Sent: Thursday, June 28, 2012 5:06 AM
To: user@cassandra.apache.org
Subject: Re: which high level Java client
i do not have experience with other clients, only hector. But timeout management in hector is really broken. If you expect your nodes to timeout often (for example, if you are using WAN) better to try something else first.
Re: which high level Java client
Posted by Radim Kolar <hs...@filez.com>.
i do not have experience with other clients, only hector. But timeout
management in hector is really broken. If you expect your nodes to
timeout often (for example, if you are using WAN) better to try
something else first.
Re: which high level Java client
Posted by Roshan <co...@gmail.com>.
Hello
We are using Hector and it perfectly matching to our case.
https://github.com/hector-client/hector
--
View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/which-high-level-Java-client-tp7580842p7580844.html
Sent from the cassandra-user@incubator.apache.org mailing list archive at Nabble.com.
Re: which high level Java client
Posted by Dan Washusen <da...@reactive.org>.
Pelops is a very thin wrapper over the Thrift client so that could be a good option.
You could also check out a fork by the VMWare/Spring guys which adds full async support: https://github.com/andrewswan/scale7-pelops. I'm not sure on the state of it, but it seems promising...
On Thursday, 28 June 2012 at 11:04 AM, James Pirz wrote:
> Dear all,
>
> I am interested in using Cassandra 1.1.1 in a read-intensive scenario, where more than 95% of my operations are get().
> I have a cluster with ~10 nodes, around 15-20 GB of data on each, while in the extreme case I expect to have 20-40 concurrent clients.
>
> I am kind of confused about which high level java client should I use ? (Which one is the best/fastest for concurrent read operations)
> Hector, Pelops, Astyanax, or something else ?
>
> I browsed the mailing list, but I came across different types of arguments and conclusions on behalf of various clients.
>
> Thanks in advance,
>
> James