THE VIDEO SHELF · message passing concurrency
Kilim: Fast, lightweight, cheap message passing in Java.
A Google Tech Talk by the author of Kilim, a Java library for lightweight actor-style message passing. It argues that message passing can replace shared-memory concurrency and claims performance competitive with or better than Erlang for huge numbers of actors.
Why HN readers recommended it
Pointed to as evidence that Java can do fast, cheap message-passing concurrency, as an alternative to Erlang or Scala actors.
This is a summary from the source dataset, not an endorsement by Hacker News or the video creator.
Video & recommendation details
- Creator / channel
- Google TechTalks
- Topic
- message passing concurrency
- Format
- talk
- Level
- advanced
- HN recommenders in dataset
- 2
- HN mentions in dataset
- 4
- Recommendation years in dataset
- 2009–2012
These counts and years describe the included Hacker News records; they are not YouTube views or the video’s publication date.
From the original HN conversations
Excerpts from the recorded comments. Follow each source for the full comment and surrounding discussion.
Actors are decoupled from the means by which they are executed. Scala has a nice system where you can run thousands of event-based actors in a thread pool. It grows the pool as needed (as threads block). See [LINK] While it may use threads, Scala's …
wynand on Hacker News · 2009-10
In Concurrency Patterns: Java, Scala, and Clojure"Asynchronious message passing is old and great idea. Instead of synchronizing objects and dealing with deadlocks we try to isolate objects and let them exchange messages. Erlang proved it to be extremly powerful tool applicable to wide range of highly scalable mission critical applications. In …
lucifer on Hacker News · 2010-02
In Why Scala Actors are Slow
Summaries, classifications and recommendation records are from the HackerTube source dataset. Read about this library and its limitations.