You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@hadoop.apache.org by Anthony Urso <an...@gmail.com> on 2010/12/08 21:40:57 UTC
Announcing KeptCollections, distributed Java Collections for ZooKeeper
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
Posted by Ted Dunning <te...@gmail.com>.
I filed an issue with a description and a suggested alternative.
On Wed, Dec 8, 2010 at 3:44 PM, Anthony Urso <an...@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 <te...@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.urso@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
Posted by Ted Dunning <te...@gmail.com>.
I filed an issue with a description and a suggested alternative.
On Wed, Dec 8, 2010 at 3:44 PM, Anthony Urso <an...@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 <te...@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.urso@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
Posted by Ted Dunning <te...@gmail.com>.
I filed an issue with a description and a suggested alternative.
On Wed, Dec 8, 2010 at 3:44 PM, Anthony Urso <an...@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 <te...@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.urso@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
Posted by Anthony Urso <an...@cs.ucla.edu>.
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 <te...@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 <an...@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
Posted by Anthony Urso <an...@cs.ucla.edu>.
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 <te...@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 <an...@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
Posted by Gaurav Sharma <ga...@gmail.com>.
Forgot to mention that the backing implementations are here:
https://github.com/gsharma/johm/tree/master/src/main/java/redis/clients/johm/collections
and you can try our JOhm from the latest jar here:
https://github.com/downloads/xetorthio/johm/johm-0.4.0.jar
On Wed, Dec 8, 2010 at 6:58 PM, Gaurav Sharma <ga...@gmail.com>wrote:
> 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 <an...@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 <ew...@gmail.com> wrote:
>> > Out of curiosity, why not just use Redis for this?
>> >
>> > On Wed, Dec 8, 2010 at 6:15 PM, Ted Dunning <te...@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.urso@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
Posted by Gaurav Sharma <ga...@gmail.com>.
Forgot to mention that the backing implementations are here:
https://github.com/gsharma/johm/tree/master/src/main/java/redis/clients/johm/collections
and you can try our JOhm from the latest jar here:
https://github.com/downloads/xetorthio/johm/johm-0.4.0.jar
On Wed, Dec 8, 2010 at 6:58 PM, Gaurav Sharma <ga...@gmail.com>wrote:
> 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 <an...@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 <ew...@gmail.com> wrote:
>> > Out of curiosity, why not just use Redis for this?
>> >
>> > On Wed, Dec 8, 2010 at 6:15 PM, Ted Dunning <te...@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.urso@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
Posted by Gaurav Sharma <ga...@gmail.com>.
Forgot to mention that the backing implementations are here:
https://github.com/gsharma/johm/tree/master/src/main/java/redis/clients/johm/collections
and you can try our JOhm from the latest jar here:
https://github.com/downloads/xetorthio/johm/johm-0.4.0.jar
On Wed, Dec 8, 2010 at 6:58 PM, Gaurav Sharma <ga...@gmail.com>wrote:
> 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 <an...@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 <ew...@gmail.com> wrote:
>> > Out of curiosity, why not just use Redis for this?
>> >
>> > On Wed, Dec 8, 2010 at 6:15 PM, Ted Dunning <te...@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.urso@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
Posted by Gaurav Sharma <ga...@gmail.com>.
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 <an...@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 <ew...@gmail.com> wrote:
> > Out of curiosity, why not just use Redis for this?
> >
> > On Wed, Dec 8, 2010 at 6:15 PM, Ted Dunning <te...@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.urso@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
Posted by Gaurav Sharma <ga...@gmail.com>.
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 <an...@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 <ew...@gmail.com> wrote:
> > Out of curiosity, why not just use Redis for this?
> >
> > On Wed, Dec 8, 2010 at 6:15 PM, Ted Dunning <te...@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.urso@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
Posted by Gaurav Sharma <ga...@gmail.com>.
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 <an...@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 <ew...@gmail.com> wrote:
> > Out of curiosity, why not just use Redis for this?
> >
> > On Wed, Dec 8, 2010 at 6:15 PM, Ted Dunning <te...@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.urso@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
Posted by Anthony Urso <an...@cs.ucla.edu>.
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 <ew...@gmail.com> wrote:
> Out of curiosity, why not just use Redis for this?
>
> On Wed, Dec 8, 2010 at 6:15 PM, Ted Dunning <te...@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 <an...@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
Posted by Anthony Urso <an...@cs.ucla.edu>.
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 <ew...@gmail.com> wrote:
> Out of curiosity, why not just use Redis for this?
>
> On Wed, Dec 8, 2010 at 6:15 PM, Ted Dunning <te...@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 <an...@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
Posted by Anthony Urso <an...@cs.ucla.edu>.
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 <ew...@gmail.com> wrote:
> Out of curiosity, why not just use Redis for this?
>
> On Wed, Dec 8, 2010 at 6:15 PM, Ted Dunning <te...@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 <an...@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
Posted by Eric Hauser <ew...@gmail.com>.
Out of curiosity, why not just use Redis for this?
On Wed, Dec 8, 2010 at 6:15 PM, Ted Dunning <te...@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 <an...@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
Posted by Anthony Urso <an...@cs.ucla.edu>.
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 <te...@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 <an...@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
Posted by Eric Hauser <ew...@gmail.com>.
Out of curiosity, why not just use Redis for this?
On Wed, Dec 8, 2010 at 6:15 PM, Ted Dunning <te...@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 <an...@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
Posted by Eric Hauser <ew...@gmail.com>.
Out of curiosity, why not just use Redis for this?
On Wed, Dec 8, 2010 at 6:15 PM, Ted Dunning <te...@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 <an...@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
Posted by Ted Dunning <te...@gmail.com>.
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 <an...@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
Posted by Patrick Hunt <ph...@apache.org>.
Anthony this looks really nice, thanks for sending it out!
Patrick
On Wed, Dec 8, 2010 at 12:40 PM, Anthony Urso <an...@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
Posted by Ted Dunning <te...@gmail.com>.
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 <an...@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
Posted by Adam Rosien <ad...@rosien.net>.
Yeah, perhaps I was a bit harsh. In my own systems I specifically
create new types that hold zk-managed data structures, e.g.
ZkSynced<T>, to inform clients that the semantics are different. You
can get copies of the current value which lets clients know the value
may change at any point.
.. Adam
On Thu, Dec 9, 2010 at 3:22 PM, Ted Dunning <te...@gmail.com> wrote:
> It definitely can go that way.
>
> But some things are pretty nicely viewed that way. For instance, wouldn't
> it be nice to have a "live processes" set in different programs? Of course,
> you have to want watch for race conditions and you can't really believe it
> is the same from moment to moment. But with those caveats, it would be
> *really* nice.
>
> On Thu, Dec 9, 2010 at 1:27 PM, Adam Rosien <ad...@rosien.net> wrote:
>
>> Making a distributed system look like a collection is a very dubious
>> proposition in my opinion. They are fundamentally different
>> abstractions and reminds me of
>> http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing.
>>
>> .. Adam
>>
>> On Wed, Dec 8, 2010 at 12:40 PM, Anthony Urso <an...@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
Posted by Adam Rosien <ad...@rosien.net>.
Yeah, perhaps I was a bit harsh. In my own systems I specifically
create new types that hold zk-managed data structures, e.g.
ZkSynced<T>, to inform clients that the semantics are different. You
can get copies of the current value which lets clients know the value
may change at any point.
.. Adam
On Thu, Dec 9, 2010 at 3:22 PM, Ted Dunning <te...@gmail.com> wrote:
> It definitely can go that way.
>
> But some things are pretty nicely viewed that way. For instance, wouldn't
> it be nice to have a "live processes" set in different programs? Of course,
> you have to want watch for race conditions and you can't really believe it
> is the same from moment to moment. But with those caveats, it would be
> *really* nice.
>
> On Thu, Dec 9, 2010 at 1:27 PM, Adam Rosien <ad...@rosien.net> wrote:
>
>> Making a distributed system look like a collection is a very dubious
>> proposition in my opinion. They are fundamentally different
>> abstractions and reminds me of
>> http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing.
>>
>> .. Adam
>>
>> On Wed, Dec 8, 2010 at 12:40 PM, Anthony Urso <an...@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
Posted by Adam Rosien <ad...@rosien.net>.
Yeah, perhaps I was a bit harsh. In my own systems I specifically
create new types that hold zk-managed data structures, e.g.
ZkSynced<T>, to inform clients that the semantics are different. You
can get copies of the current value which lets clients know the value
may change at any point.
.. Adam
On Thu, Dec 9, 2010 at 3:22 PM, Ted Dunning <te...@gmail.com> wrote:
> It definitely can go that way.
>
> But some things are pretty nicely viewed that way. For instance, wouldn't
> it be nice to have a "live processes" set in different programs? Of course,
> you have to want watch for race conditions and you can't really believe it
> is the same from moment to moment. But with those caveats, it would be
> *really* nice.
>
> On Thu, Dec 9, 2010 at 1:27 PM, Adam Rosien <ad...@rosien.net> wrote:
>
>> Making a distributed system look like a collection is a very dubious
>> proposition in my opinion. They are fundamentally different
>> abstractions and reminds me of
>> http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing.
>>
>> .. Adam
>>
>> On Wed, Dec 8, 2010 at 12:40 PM, Anthony Urso <an...@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
Posted by Ted Dunning <te...@gmail.com>.
It definitely can go that way.
But some things are pretty nicely viewed that way. For instance, wouldn't
it be nice to have a "live processes" set in different programs? Of course,
you have to want watch for race conditions and you can't really believe it
is the same from moment to moment. But with those caveats, it would be
*really* nice.
On Thu, Dec 9, 2010 at 1:27 PM, Adam Rosien <ad...@rosien.net> wrote:
> Making a distributed system look like a collection is a very dubious
> proposition in my opinion. They are fundamentally different
> abstractions and reminds me of
> http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing.
>
> .. Adam
>
> On Wed, Dec 8, 2010 at 12:40 PM, Anthony Urso <an...@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
Posted by Ted Dunning <te...@gmail.com>.
It definitely can go that way.
But some things are pretty nicely viewed that way. For instance, wouldn't
it be nice to have a "live processes" set in different programs? Of course,
you have to want watch for race conditions and you can't really believe it
is the same from moment to moment. But with those caveats, it would be
*really* nice.
On Thu, Dec 9, 2010 at 1:27 PM, Adam Rosien <ad...@rosien.net> wrote:
> Making a distributed system look like a collection is a very dubious
> proposition in my opinion. They are fundamentally different
> abstractions and reminds me of
> http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing.
>
> .. Adam
>
> On Wed, Dec 8, 2010 at 12:40 PM, Anthony Urso <an...@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
Posted by Ted Dunning <te...@gmail.com>.
It definitely can go that way.
But some things are pretty nicely viewed that way. For instance, wouldn't
it be nice to have a "live processes" set in different programs? Of course,
you have to want watch for race conditions and you can't really believe it
is the same from moment to moment. But with those caveats, it would be
*really* nice.
On Thu, Dec 9, 2010 at 1:27 PM, Adam Rosien <ad...@rosien.net> wrote:
> Making a distributed system look like a collection is a very dubious
> proposition in my opinion. They are fundamentally different
> abstractions and reminds me of
> http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing.
>
> .. Adam
>
> On Wed, Dec 8, 2010 at 12:40 PM, Anthony Urso <an...@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
Posted by Anthony Urso <an...@cs.ucla.edu>.
Any specific fallacy or objection? Or is this intentionally vague?
On Thu, Dec 9, 2010 at 1:27 PM, Adam Rosien <ad...@rosien.net> wrote:
> Making a distributed system look like a collection is a very dubious
> proposition in my opinion. They are fundamentally different
> abstractions and reminds me of
> http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing.
>
> .. Adam
>
> On Wed, Dec 8, 2010 at 12:40 PM, Anthony Urso <an...@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
Posted by Adam Rosien <ad...@rosien.net>.
Making a distributed system look like a collection is a very dubious
proposition in my opinion. They are fundamentally different
abstractions and reminds me of
http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing.
.. Adam
On Wed, Dec 8, 2010 at 12:40 PM, Anthony Urso <an...@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
Posted by Ashwin Jayaprakash <as...@gmail.com>.
Nice!
Basic data structure abstractions are what we really need in most use cases.
--
View this message in context: http://zookeeper-user.578899.n2.nabble.com/Announcing-KeptCollections-distributed-Java-Collections-for-ZooKeeper-tp5816709p5821492.html
Sent from the zookeeper-user mailing list archive at Nabble.com.
Re: Announcing KeptCollections, distributed Java Collections for
ZooKeeper
Posted by David Rosenstrauch <da...@darose.net>.
On 12/08/2010 03:40 PM, Anthony Urso 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.
Sounds very similar in functionality to Terracotta. (Though quite
different in implementation.)
Anyway, great work!
DR
Re: Announcing KeptCollections, distributed Java Collections for ZooKeeper
Posted by Adam Rosien <ad...@rosien.net>.
Making a distributed system look like a collection is a very dubious
proposition in my opinion. They are fundamentally different
abstractions and reminds me of
http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing.
.. Adam
On Wed, Dec 8, 2010 at 12:40 PM, Anthony Urso <an...@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
Posted by Ted Dunning <te...@gmail.com>.
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 <an...@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
Posted by Patrick Hunt <ph...@apache.org>.
Anthony this looks really nice, thanks for sending it out!
Patrick
On Wed, Dec 8, 2010 at 12:40 PM, Anthony Urso <an...@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
Posted by Adam Rosien <ad...@rosien.net>.
Making a distributed system look like a collection is a very dubious
proposition in my opinion. They are fundamentally different
abstractions and reminds me of
http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing.
.. Adam
On Wed, Dec 8, 2010 at 12:40 PM, Anthony Urso <an...@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
>