Re: Announcing KeptCollections, distributed Java Collections for ZooKeeper
Out of curiosity, why not just use Redis for this? On Wed, Dec 8, 2010 at 6:15 PM, Ted Dunning ted.dunn...@gmail.com wrote: This looks very useful and looks like nice work. I note that the methods used are prone to race conditions, but if you are just thinking about shared maps, this probably isn't important. On Wed, Dec 8, 2010 at 12:40 PM, Anthony Urso anthony.u...@gmail.comwrote: I am pleased to announce the initial release of KeptCollections, a library of drop-in replacements for standard Java Collections that use Apache ZooKeeper as a backing store. KeptCollections are designed to make it easy for anyone to write distributed applications without having to learn the intricacies of ZooKeeper, or distributed programming in general. The collections use the well-known JDK APIs, yet any changes made to any of these collections by one node are seen by all other nodes within milliseconds, allowing for easy communication between processes in a computing cluster. More information here: https://github.com/anthonyu/KeptCollections/wiki and all code is available from: https://github.com/anthonyu/KeptCollections Please try it out, and let me know any problems you experience via github issues or this email address. Cheers, Anthony
Re: Announcing KeptCollections, distributed Java Collections for ZooKeeper
Oh, thanks for the heads up on the race conditions. I'd like to eliminate them all, so let me know specifics and I will work on them, or just send a patch if you see an obvious solution. Thanks for the feedback! Anthony On Wed, Dec 8, 2010 at 3:15 PM, Ted Dunning ted.dunn...@gmail.com wrote: This looks very useful and looks like nice work. I note that the methods used are prone to race conditions, but if you are just thinking about shared maps, this probably isn't important. On Wed, Dec 8, 2010 at 12:40 PM, Anthony Urso anthony.u...@gmail.comwrote: I am pleased to announce the initial release of KeptCollections, a library of drop-in replacements for standard Java Collections that use Apache ZooKeeper as a backing store. KeptCollections are designed to make it easy for anyone to write distributed applications without having to learn the intricacies of ZooKeeper, or distributed programming in general. The collections use the well-known JDK APIs, yet any changes made to any of these collections by one node are seen by all other nodes within milliseconds, allowing for easy communication between processes in a computing cluster. More information here: https://github.com/anthonyu/KeptCollections/wiki and all code is available from: https://github.com/anthonyu/KeptCollections Please try it out, and let me know any problems you experience via github issues or this email address. Cheers, Anthony
Re: Announcing KeptCollections, distributed Java Collections for ZooKeeper
I filed an issue with a description and a suggested alternative. On Wed, Dec 8, 2010 at 3:44 PM, Anthony Urso antho...@cs.ucla.edu wrote: Oh, thanks for the heads up on the race conditions. I'd like to eliminate them all, so let me know specifics and I will work on them, or just send a patch if you see an obvious solution. Thanks for the feedback! Anthony On Wed, Dec 8, 2010 at 3:15 PM, Ted Dunning ted.dunn...@gmail.com wrote: This looks very useful and looks like nice work. I note that the methods used are prone to race conditions, but if you are just thinking about shared maps, this probably isn't important. On Wed, Dec 8, 2010 at 12:40 PM, Anthony Urso anthony.u...@gmail.com wrote: I am pleased to announce the initial release of KeptCollections, a library of drop-in replacements for standard Java Collections that use Apache ZooKeeper as a backing store. KeptCollections are designed to make it easy for anyone to write distributed applications without having to learn the intricacies of ZooKeeper, or distributed programming in general. The collections use the well-known JDK APIs, yet any changes made to any of these collections by one node are seen by all other nodes within milliseconds, allowing for easy communication between processes in a computing cluster. More information here: https://github.com/anthonyu/KeptCollections/wiki and all code is available from: https://github.com/anthonyu/KeptCollections Please try it out, and let me know any problems you experience via github issues or this email address. Cheers, Anthony
Re: Announcing KeptCollections, distributed Java Collections for ZooKeeper
For those interested in a Redis Collections implementation, please take a look here: https://github.com/gsharma/johm/tree/master/src/main/java/redis/clients/johm specifically the CollectionMap, CollectionSet, CollectionSortedSet, CollectionList classes. On Wed, Dec 8, 2010 at 6:48 PM, Anthony Urso antho...@cs.ucla.edu wrote: Eric: This is pretty different from redis, but a Java Collections interface to redis would be awesome, too. Cheers, Anthony On Wed, Dec 8, 2010 at 3:33 PM, Eric Hauser ewhau...@gmail.com wrote: Out of curiosity, why not just use Redis for this? On Wed, Dec 8, 2010 at 6:15 PM, Ted Dunning ted.dunn...@gmail.com wrote: This looks very useful and looks like nice work. I note that the methods used are prone to race conditions, but if you are just thinking about shared maps, this probably isn't important. On Wed, Dec 8, 2010 at 12:40 PM, Anthony Urso anthony.u...@gmail.com wrote: I am pleased to announce the initial release of KeptCollections, a library of drop-in replacements for standard Java Collections that use Apache ZooKeeper as a backing store. KeptCollections are designed to make it easy for anyone to write distributed applications without having to learn the intricacies of ZooKeeper, or distributed programming in general. The collections use the well-known JDK APIs, yet any changes made to any of these collections by one node are seen by all other nodes within milliseconds, allowing for easy communication between processes in a computing cluster. More information here: https://github.com/anthonyu/KeptCollections/wiki and all code is available from: https://github.com/anthonyu/KeptCollections Please try it out, and let me know any problems you experience via github issues or this email address. Cheers, Anthony
