announce: lettuce 1.0.0, a Java NIO redis client

[Will]

Hello,

I'm happy to announce lettuce, a new Java client for redis, available
at http://github.com/wg/lettuce and in the central maven repo:

<dependency>
<groupId>com.lambdaworks</groupId>
<artifactId>lettuce</artifactId>
<version>1.0.0</version>
</dependency>

Lettuce is a scalable thread-safe client built on top of the excellent
netty framework. Multiple threads can share a single connection as
long as they avoid blocking and transactional operations, and multiple
connections are efficiently managed using NIO selectors.

Internally lettuce is completely asynchronous and it exposes both
synchronous and asynchronous interfaces, as well as asynchronous
pub/sub callbacks.

Lettuce doesn't come with built-in support for sharding, but I do plan
to support Redis Cluster.

Enjoy!
Will

[David Yu]

Nice.  All the bloat that comes with netty.  Why not use the lean jedis?

--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To post to this group, send email to redi...@googlegroups.com.
To unsubscribe from this group, send email to redis-db+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/redis-db?hl=en.

--
When the cat is away, the mouse is alone.
- David Yu

[Derek Williams]

On Thu, Mar 24, 2011 at 7:49 AM, David Yu <david....@gmail.com> wrote:
> Nice.  All the bloat that comes with netty.  Why not use the lean jedis?

Due to Redis's simple protocol and high performance it can be fun to
create your own client, I learned a lot by doing the same thing (in
Scala).

I've never programmed in Java before so I'm not as up to speed on the
pros and cons of different NIO frameworks but I am using HawtDispatch
(http://hawtdispatch.fusesource.org/) with great success. Does Netty
not have a good reputation?

--
Derek

[Will]

On Mar 24, 10:49 pm, David Yu <david.yu....@gmail.com> wrote:
> Nice.  All the bloat that comes with netty.  Why not use the lean jedis?

Jedis is great, I use it myself and think it's a good choice for the
recommended client for Java.

If your workload is compatible with blocking IO and your connections
can't be shared between multiple threads then by all means use Jedis,
it's faster in that scenario and being more mature almost certainly
has fewer bugs.

Lettuce is a complementary product, you might choose it for a number
of reasons:

* significantly faster when one connection is shared with many threads
* supports key and/or value types other than String and byte[]
* should efficiently support large numbers of idle connections (pub/
sub, blpop)

-Will

> On Thu, Mar 24, 2011 at 8:30 PM, Will <wglo...@gmail.com> wrote:
> > Hello,
>
> > I'm happy to announce lettuce, a new Java client for redis, available

> > athttp://github.com/wg/lettuceand in the central maven repo: