Concurrency

The actors model is a programming model that makes it easy to reason about highly concurrent applications. It occurred to me that I've never read an article that explains why this model is better than the traditional model of threads and locks. So I thought I'd write my opinion on this.

 

First, actors are an abstraction. At the end, code is run on a traditional CPU and OS and so it uses threads and locks. Actors just let us, the developers, forget about these details, like OO where objects don't really exist at the machine level.

 

ittayd 11/12/2009 - 22:10

Hello,

 

I would like to share my bad and good experience in application's design and planning.

 

1)

Remember, if you work with WEB/EJB container's objects, never make assumptions.

This stuff always tends to behave against your common sense.

As example:

peterk 10/09/2009 - 16:25

The java threading is obviously the best of the threading paradigms we have!

(Now I squeeze my ears to avoid the loud and uncontrollable, sometimes even hateful reaction)

They just bark : “Scala is the right threading, you will do better with Scala”.

Ok..Ok..Relax...

You can call that wrapper a language and fully enjoy it .

But somebody, even more skeptic than me has said: “Java is a C and an Assembly wrapper, so why it is a language and scala is not?”

I appreciate all those comments and have a right to completely ignore them.
Yes.

peterk 09/06/2009 - 10:34

A series of 4 articles about parallel comuting in Java:

admin 07/09/2008 - 01:38

The 'Phaser' concept and name was coined in this whitepaper by a team at Rice University. The name comes from the construct's phase-ordering and deadlock-avoidance properties. The whitepaper explains several details of the phaser concept.

zvika 10/08/2008 - 16:59
Syndicate content