Next NoSQL Summer Vancouver Event: July 26 -- Google's MapReduce

[cclark]

The initial details for the next session have been posted on the Group
wiki.

We're still looking for a blog post on Vector Clocks. If you know of
any or come across one you think would be worthwhile to discuss please
suggest it to the group.

Click on http://groups.google.com/group/nosql-summer-vancouver/web/july-26----googles-mapreduce
- or copy & paste it into your browser's address bar if that doesn't
work.

[Howard Yeh]

> We're still looking for a blog post on Vector Clocks.  If you know of
> any or come across one you think would be worthwhile to discuss please
> suggest it to the group.

from basho, a down to earth, informal explanation. gives the intuition
behind vector clocks.

http://blog.basho.com/2010/01/29/why-vector-clocks-are-easy/

[Tavis Rudd]

How about this one and the posts from the Riak guys that it
references
('Why vector clocks are [easy|hard]' which Howard suggests and someone
mentioned on
Monday)?

http://nosql.mypopescu.com/post/524128219/learn-about-conflict-resolution-and-vector-clocks

They're all quite
short.

[cclark]

Well there hasn't been much more thrown out there. The two blog posts
are relatively short so let's say the extra credit reading for this
week is:

- http://blog.basho.com/2010/01/29/why-vector-clocks-are-easy/
- http://blog.basho.com/2010/04/05/why-vector-clocks-are-hard/

I'm looking forward to a good discussion about MapReduce and Vector
Clocks.

thanks,
chuck

On Jul 15, 9:19 pm, Tavis Rudd <tavis.r...@gmail.com> wrote:
> How about this one and the posts from the Riak guys that it
> references
> ('Why vector clocks are [easy|hard]' which Howard suggests and someone
> mentioned on
> Monday)?
>

> http://nosql.mypopescu.com/post/524128219/learn-about-conflict-resolu...