Concurrent- Parallel- Networked- Distributed- Computing

1. Contemporary
2. Simultaneous
   1. walk and chew gum
3. Sharing and Ownership
4. Synergy

www.merriam-webster.com

1. syn.er.gy noun {si-ner-jea} : the increased effectiveness that results when two or more people or businesses work together. Plural synergies
2. synergism; broadly: combined action or operation
3. a mutually advantageous conjunction or compatibility of distinct business participants or elements (as resources or efforts)
4. Examples of SYNERGY:
   1. A synergy has developed among the different groups working on this project.
   2. two companies that have found synergy

http://wordnet.princeton.edu/

1. Noun 1. synergy - the working together of two things (muscles or drugs for example) to produce an effect greater than the sum of their individual effects
2. potentiation = (medicine) the synergistic effect of two drugs given simultaneously

1. Networked Computing + Synergy
2. Processes communicate only via send and receive.
   1. Loss of messages? No.
   2. Order of sends = Order of receives? Yes?
3. Processes do not have shared state/ memory.

1. Independent lives? Yes;
2. Cooperative? Yes;
3. Contentious? No;
4. Malicious? No.

1. How do they "know" each other?
   1. Established naming protocols
   2. PL support
2. Scalabe? Yes. (Note the "but" part in networked computing.)
3. Nondeterminism (our fat-bar)

1. x := a by P1 vs x := b by P2 vs read x by P3
2. Must P3 be able to see: a and/or b? when?
3. Are we assuming priorities among P1, P2, P3?
4. Global clock?
5. Unclear semantics; implied expections of "memory"

1. Large, Conceptually One, "Data Structure". Databases.
2. Partitioned and stored across many nodes.
3. Migrate the partitions as needed.
4. Replicate some partitions for reads, track writes

1. Assumes multiple processors/ cores.
2. Assumes shared memory.
3. Assumes life-times of processes overlap.
4. Assumes arbitrarily fine granularity
   1. memory read v write v write by different cores
   2. E.g., a += b and simultaneouly c -= d
      1. Could a be an alias for c?

1. Permits but does not assume multiple processors/ cores.
2. Permits but does not assume shared memory.
3. Permits but does not assume life-times of processes overlap.
4. Assumes "not-so-fine" granularity of execution of basic instructions.

1. Higher level abstract view
2. Mutual exclusion of code segments
3. Synchronization of indpendent processes
4. Send and receive messages