Withdraw
Loading…
Why Do Scala Developers Mix the Actor Model with Other Concurrency Models?
Tasharofi, Samira; Dinges, Peter; Johnson, Ralph E.
Content Files

Loading…
Download Files
Loading…
Download Counts (All Files)
Loading…
Edit File
Loading…
Permalink
https://hdl.handle.net/2142/34816
Description
- Title
- Why Do Scala Developers Mix the Actor Model with Other Concurrency Models?
- Author(s)
- Tasharofi, Samira
- Dinges, Peter
- Johnson, Ralph E.
- Issue Date
- 2012-10-14
- Keyword(s)
- concurrent programs
- actor model
- Scala
- Date of Ingest
- 2012-10-26T16:53:10Z
- Abstract
- Mixing the actor model with other concurrency models in a single program can break the actor abstraction. This increases the chance of creating deadlocks and data races—two mistakes that are hard to make with actors. Furthermore, it prevents the use of many advanced testing, modeling, and verification tools for actors, as these require pure actor programs. This study is the first to point out the phenomenon of mixing concurrency models and to systematically identify the factors leading to it. We studied 15 large, mature, and actively maintained actor programs written in Scala and found that 80% of them mix the actor model with another concurrency model. Consequently, a large part of real-world actor programs does not use actors to their fullest advantage. Inspection of the programs and discussion with the developers reveal two reasons for mixing that can be influenced by researchers and library-builders: weaknesses in the actor library implementations, and shortcomings of the actor model itself.
- Type of Resource
- text
- Genre of Resource
- Technical Report
- Language
- en
- Permalink
- http://hdl.handle.net/2142/34816
Owning Collections
Manage Files
Loading…
Edit Collection Membership
Loading…
Edit Metadata
Loading…
Edit Properties
Loading…
Embargoes
Loading…