Hi,
We, ActiveState, also have a fork of Doozerd, in which we have implemented ephemeral nodes. We use this extensively in our product,
Stackato. The ephemeral nodes really help in getting an overview of processes running state throughout a cluster.
Bit more background here...
We have not put a great deal of effort in doozerd development and are limited on the resources we can assign to it. Some of the work we have done is on the Ruby client libraries, but some of that work is specific to our implementation.
We have found several limitations with Doozerd, we would like to address, but we are also considering alternatives such as ZooKeeper or some other (more light-weight than ZK) clustered key-value implementation. We depend on several features of doozerd, most notably watchers, ephemeral nodes, clustering and being light-weight.
Limitations we've found include... it degrades rapidly the more values you put in, it's slow to get a group of config values in one go (lots of tcp packets back-and-forth), becomes disabled if you post large values (3kb) requiring restart. Generally it's slow, for what it does, even with a single doozerd instance, which surprises me since it's data is all in RAM.
We are limited on development time we can commit to this, but we do have insights into using doozerd, as it's been a part of our product for a little while now. We would love to talk more.
Cheers,
Phil