AsyncFP

Facebook Twitter

Asynchronous Functional Programming, just starting work on a kit for building custom NoSql databases. Oct 13

One of the key performance attributes for Actors is the speed with which messages can be consumed and processed. If the overhead of messaging is too high then Actors can't be used for solving some types of concurrency problems. Ideally the overhead of an Actor should be similar to method calls to make it generally useful, although some overhead has to be expected. While implementing a simple CountingActor in Scala I noticed lower than expected performance and I decided to compare it to an Erlang OTP gen_server implementation. Krazy Koding: Scala Actor v Erlang gen_server Performance Krazy Koding: Scala Actor v Erlang gen_server Performance
Paxos (computer science)

Paxos (computer science)

Consensus protocols are the basis for the state machine approach to distributed computing, as suggested by Leslie Lamport[2] and surveyed by Fred Schneider.[3] The state machine approach is a technique for converting an algorithm into a fault-tolerant, distributed implementation. Ad-hoc techniques may leave important cases of failures unresolved. The principled approach proposed by Lamport et al. ensures all cases are handled safely. The Paxos protocol was first published in 1989 and named after a fictional legislative consensus system used on the Paxos island in Greece.[4] It was later published as a journal article in 1998.[5]
Why AsyncFP.pdf
Data Integrity.pdf
AsyncFP Basics.pdf
Wiki

Links of Interest

AgileWikiDevelopers
Other google groops

Download
NoSQL

Other Pearltrees