Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m looking for a good slideshow/pdf/video explaining the differences in approach and thinking from hand-written threading of applications compared to the more abstracted and easier to use message passing and actor models. Does anyone know of existing resources to explain these concepts with good diagrams and visualizations?
It is slightly difficult to make direct comparisons without long, painful digressions, or a largely theoretical discussion. However, the following can be easily read, and I believe that the comparisons will form naturally for anyone familiar with the threading model.
Google’s language GO uses message passing among co-routines as a core part of its concurrency model. There is a lot more information on GO at golang.org, and the following URL provides information about their concurrency model in GO.
This is a paper written by Edward Lee (Berkeley EECS department chair) called The Problem with Threads. It is a pitch for the actor model, and is a good read. Also note that there are other papers by Edward that deal with the problem with threads (visit his homepage for more papers).