Re: Re[2]: Comparison of high-level concurrency models?

For distributed workflow, you need (and may have) looked at the
map-reduce model and the open source hadoop implementation.  It is
being used by yahoo!, facebook, veoh, and others and is a nice, easy
to understand distributed model.

Check out http://hadoop.apache.org

On Tue, May 27, 2008 at 5:10 PM, Gregg Irwin <[email protected]> wrote:
> Hi John,
>
>>> I'm looking for a comparison of high-level concurrency models such as
>>> Actors, Tuplespace, Software Transactional Memory, and others that I
>>> may not have heard of.
>
> JC> And so, since I have burnt and crispy fingers, from playing with
> JC> concurrency....
>
> JC> The only solutions on that I personally will believe in are ones which
> JC> are mind bogglingly simple... and impose harsh, but simplifying
> JC> restrictions on the programmers.
>
> This being the prag list, and hoping to save my own fingers from as
> much crispiness as possible, what would be the "harsh, but simplifying
> restrictions" you would impose, or what models/lanugages worked for
> you (or didn't)? My context is more distributed workflow oriented than
> pure HPC, but any thoughts based on your experience would be most
> welcome.
>
> Thanks,
>
> --Gregg
>
>