disque

The use case would be implementing the redis protocol for client server communication in your own software. There is a specification for using the redis protocol [1]. The fact that redis is widely used and there are a number of client libraries in many languages may make it an attractive option compared to creating your own protocol from scratch. I believe disque, the distributed message broker [2] uses the redis protocol for client server communication. [1] http://redis.io/topics/protocol [2] https://github.com/antirez/disque

I run Postgres, MonetDB, Redis, and Disque on DragonFlyBSD for various hobby projects. It's been extremely stable, easy to administer¹, and fast². Two of my favorite things: 1. HAMMER, and the upcoming HAMMER2, are very nice filesystems. HAMMER isn't a CoW fs like ZFS and btrfs; HAMMER2 is however. Also, somehow HAMMER2 is more stable than btrfs despite having about 3 developers. 2. Like Solaris, DragonFly isn't afraid to deviate from and advance traditional *nix design. vkernels, lightweight threads, a super cool message-passing API, NT-esque architecture of a decoupled microkernel-ish design running in one address space, etc. It also has neat cluster features not unlike VMS and Plan9, but I haven't used them. -- ¹ I use FreeBSD as a desktop OS so my opinion here could be a bit skewed. But I think, like most BSDs, it's a very well-though