[erlang-questions] How to Name Concurrency Patterns
Thu Feb 20 00:12:47 CET 2014
There's a reasonable collection of resources here for parallel patterns:
POSA2 probably has the most accessible and well known concurrency patterns:
POSA4 has a reasonable set for distributed systems, at least the well known
Another good one is The Art of Multiprocessor Programming:
Naming sucks though. An audience with Java/JVM experience may know of
the LMAX Disruptor and maybe the coalescing ring buffer but that level of
detail may be too audience specific. Or, being general, these are just queue
Forgetting the patterns for a minute. Making sure Amdahl, Little and
are known and understood would be a good start. Possibly with explaining
being concurrent, parallel or simultaneous means. Good foundations
of the terminology ultimately chosen...
On Wed, Feb 19, 2014 at 10:48 PM, Miles Fidelman <mfidelman@REDACTED
> Joe Armstrong wrote:
>> Ptolemy and his mates thought the planets moved in epicyles, they make
>> wonderful drawings
>> of this, and gave examples - trouble was they were all wrong. Good old
>> Kepler put them
>> right with a few equations.
> Of course the numerical algorithms used to produce navigational tables
> look suspiciously like cycles and epicycles :-)
>> I would be interested to hear what name people suggest, but I'm
>> afraid there's about as many concurrency patterns as there are
>> possible combinations.
>> Yes - but names like gen_server supervisor, gen_fsm are useful to express
>> designs (to people who know
>> OTP) but we need more well know names
> how about supervisor and finite state machine - pretty standard terminology
>> I suggest calling the DNS pattern Howard and the load
>> balancer-replacement pattern Clementine.
>> How about Fred (as in "Let Fred do it" - the generic autopilot), or
> George (as in "I'll love him, and hug him, and call him George.") :-)
> In theory, there is no difference between theory and practice.
> In practice, there is. .... Yogi Berra
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions