Erlang Land を読んでErlangを学んだ。 Erlangの並列処理を学ぶことでアクターモデルの理解ができた! 概念的に理解できてなかったScalaのActorライブラリも読み書きができるようになりました。 Erlangの並列版フィボナッチをScalaで書いてみました。 import scala.actors._ class FibActor(var name:String) extends Actor { def act = { receive { case i:Int => println(name + ": " + fib(i)) } } def fib(n:Int):Int = { n match { case 0 => 1 case 1 => 1 case _ => fib(n - 1) + fib(n - 2) } } } object ActorTest { def
Very simple distributed Task queue that allow the scheduling of job functions to be executed on local or remote workers. Can be seen as a Proof of Concept leveraging ZMQ sockets and cloudpickle serialization capabilities as well as a very basic actor system to handle different loads of work from connecting clients. Originally it was meant to be just a brokerless job queue, recently I dove deeper o
Implementing an actor pattern that integrates with C#’s async/await keywords using less well-known regions of the .NET Task Parallel Library The actor is a widely used pattern in concurrency with strong support in languages such as Erlang and Scala. Rather than sharing data between threads and having to use locking mechanisms to synchronise access, the actor is a single entity that is responsible
In computer science, message passing is a technique for invoking behavior (i.e., running a program) on a computer. The invoking program sends a message to a process (which may be an actor or object) and relies on that process and its supporting infrastructure to then select and run some appropriate code. Message passing differs from conventional programming where a process, subroutine, or function
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く