Another option besides Steve's excellent one would be to keep something like 1000 nodes in your list per znode. Many update patterns will give you the same number of updates, but the ZK transactions that result (getChildren, read znode) will likely be more efficient, especially the getChildren call.
Remember, it is not a requirement that you have a one-to-one mapping between your in-memory objects and in-zookeeper znodes. If that works, fine. If not, feel free to be creative. On Mon, Aug 2, 2010 at 7:45 AM, Steve Gury <steve.g...@mimesis-republic.com>wrote: > Is there any recipe that would provide this feature (or a work around) ? >
