heckenlights-logoWeihnachten ist das Fest der Liebe, Freude und des Lichts. Weihnachtsdekorationen rund um die Welt zieren Häuser, Straßen und Bäume.

Der Christmas Spirit Tree hat im Internet der Dinge den Start gemacht und das Online-Unvisersum (Tweets und Blogs) auf einen Weihnachtsbaum gebracht. Im Heckenpfad in Weinheim erwachen ab dem 1. Dezember die Lichter der interaktiven Weihnacht mit einer Show, deren Programm in der Hand des Zuschauers liegt.

Read more ...

Elasticsearch, Logstash and Kibana are widely used for log management. I wrote in earlier posts about submitting application logs towards logstash. Let’s approach access logs today.

Read more ...

heckenlights-logoChristmas means joy, love and light to us. Cities, houses and streets are decorated for christmas all around the world.

Christmas has reached the internet, too. The Christmas Spirit Tree was one of the first christmas-themed things of the internet. It showed movement in the social universe of tweets and blogs. And here, in Heckenpfad, Weinheim, Germany, the sparkle of Heckenlights will launch on December 1st. Lights will switch on for admiring and listening.

Read more ...

A choice of decision for a NoSQL data store depends on several factors. It's no longer a hot-or-not decision. The big hype is over, reality comes back now.

Read more ...

Some years ago I moved into my own home. At that time I had the idea to setup christmas lights in our garden. Maybe not as large as Carson Williams setup, but at least something. And well, you know, it grew from year to year. Now I came to the point where I want give you control over the lights.

Read more ...

lettuce 3.0.1 was released. This is a bugfix release fixing some major bugs.

This release contains:

Fixes

  • Test improvements for more stability
  • URI for sentinel connections
  • Provide static syncHandler
  • Handle premature channelInactive while ongoing close (avoid NPE)
  • Fix signature of clusterSlaves #18
  • Fix SCAN command with scan args

Enhancements

  • Optimized CRC16 calculation (thanks to Jedis for co-working)
  • Use fine grained exceptions for Timeout, CommandExecution and Connection

Links

Maven coordinates:

<dependency>
    <groupId>biz.paluch.redis</groupId>
    <artifactId>lettuce</artifactId>
    <version>3.0.1.Final</version>
</dependency>

<dependency>
    <groupId>biz.paluch.redis</groupId>
    <artifactId>lettuce</artifactId>
    <version>3.0.1.Final</version>
    <classifier>shaded</classifier>
</dependency>

Any feedback is appreciated or create issues on GitHub.

Some time ago, I wrote about finding the right NoSQL data store. It depends pretty much on what you want to do. After a series of tests I finally have some results I want to share. My goal: Find the most appropriate NoSQL data store for our project's use case.

Requirements

The requirements is to parse XML files which are stored on a storage system and put relevant keys into a data store to be able to find the data again. It's a sort of index. The data is hierarchical with two levels (master and detail). The data stream is continuous and there is a lot of data (not big data). 10's of TB's.

Read more ...

lettuce 3.0 was released. Lettuce is a scalable thread-safe Redis client providing both synchronous and asynchronous connections. Multiple threads may share one connection provided they avoid blocking and transactional operations such as BLPOP, and MULTI/EXEC. Multiple connections are efficiently managed by the excellent netty NIO framework. Support for advanced Redis features such as Sentinel, Cluster and Redis data models are included.

Some of the major changes are:

  • Support for the latest Redis commands
  • Redis Cluster support
  • Redis Sentinel support
  • Upgrade to netty 4.0.19 (from netty 3.x)
  • CDI and Spring support
  • Streaming API
  • Listenable Futures (using Guava) for true async operations
  • Tons of bugfixes, tests and documentation

Lettuce 3.0 is a fork of original lettuce@wg with preserved packages and mostly the same API. The original lettuce is no longer in active development.

What's next?

My plan is to keep up with tight Redis development and to integrate the new fork into Spring Data Redis. Redis Cluster has to get mature, and the current implementation has to prove in production.

Links

Maven coordinates:

<dependency>
    <groupId>biz.paluch.redis</groupId>
    <artifactId>lettuce</artifactId>
    <version>3.0.Final</version>
</dependency>

<dependency>
    <groupId>biz.paluch.redis</groupId>
    <artifactId>lettuce</artifactId>
    <version>3.0.Final</version>
    <classifier>shaded</classifier>
</dependency>

Any feedback is appreciated or create issues on GitHub.

I released today logstash-gelf 1.5.4. This release carries some internal improvements if you plan to extend log appenders and GELF senders.

Read more ...

I've released today logstash-gelf 1.5.3. This is a bugfix release for Hadoop Hive users. I did not announce release 1.5.2 the last time. Apologies for that.

Read more ...