A node ID is a string that uniquely identifies the node within a network. Depending on the configuration used, node IDs can look like a hostname, a hostname and a port, or a random string. AnyEvent::MP itself doesn't interpret node IDs in any way.

Nodes can only talk to each other by creating some kind of connection to each other. To do this, nodes should listen on one or more local transport endpoints - binds. Currently, only standard ip:port specifications can be used, which specify TCP ports to listen on.

When a node starts, it knows nothing about the network. To teach the node about the network it first has to contact some other node within the network. This node is called a seed.

Apart from the fact that other nodes know them as seed nodes and they have to have fixed listening addresses, seed nodes are perfectly normal nodes - any node can function as a seed node for others.

In addition to discovering the network, seed nodes are also used to maintain the network and to connect nodes that otherwise would have trouble connecting. They form the backbone of an AnyEvent::MP network.

Seed nodes are expected to be long-running, and at least one seed node should always be available. They should also be relatively responsive - a seed node that blocks for long periods will slow down everybody else.

Seeds are transport endpoint(s) (usually a hostname/IP address and a TCP port) of nodes that should be used as seed nodes.

The nodes listening on those endpoints are expected to be long-running, and at least one of those should always be available. When nodes run out of connections (e.g. due to a network error), they try to re-establish connections to some seednodes again to join the network.

Before a node can talk to other nodes on the network (i.e. enter "distributed mode") it has to configure itself - the minimum a node needs to know is its own name, and optionally it should know the addresses of some other nodes in the network to discover other nodes.

The key/value pairs are basically the same ones as documented for the aemp command line utility (sans the set/del prefix).

This function configures a node - it must be called exactly once (or never) before calling other AnyEvent::MP functions.

The function first looks up a profile in the aemp configuration (see the aemp commandline utility). The profile name can be specified via the named profile parameter or can simply be the first parameter). If it is missing, then the nodename (uname -n) will be used as profile name.

The profile data is then gathered as follows:

First, all remaining key => value pairs (all of which are conveniently undocumented at the moment) will be interpreted as configuration data. Then they will be overwritten by any values specified in the global default configuration (see the aemp utility), then the chain of profiles chosen by the profile name (and any parent attributes).

That means that the values specified in the profile have highest priority and the values specified directly via configure have lowest priority, and can only be used to specify defaults.

If the profile specifies a node ID, then this will become the node ID of this process. If not, then the profile name will be used as node ID. The special node ID of anon/ will be replaced by a random node ID.

The next step is to look up the binds in the profile, followed by binding aemp protocol listeners on all binds specified (it is possible and valid to have no binds, meaning that the node cannot be contacted form the outside. This means the node cannot talk to other nodes that also have no binds, but it can still talk to all "normal" nodes).

If the profile does not specify a binds list, then a default of * is used, meaning the node will bind on a dynamically-assigned port on every local IP address it finds.

Send the given message to the given port, which can identify either a local or a remote port, and must be a port ID.

While the message can be almost anything, it is highly recommended to use a string as first element (a port ID, or some word that indicates a request type etc.) and to consist if only simple perl values (scalars, arrays, hashes) - if you think you need to pass an object, think again.

The message data logically becomes read-only after a call to this function: modifying any argument (or values referenced by them) is forbidden, as there can be considerable time between the call to snd and the time the message is actually being serialised - in fact, it might never be copied as within the same process it is simply handed to the receiving port.

The type of data you can transfer depends on the transport protocol: when JSON is used, then only strings, numbers and arrays and hashes consisting of those are allowed (no objects). When Storable is used, then anything that Storable can serialise and deserialise is allowed, and for the local node, anything can be passed. Best rely only on the common denominator of these.

Creates a new local port, and returns its ID. Semantically the same as creating a port and calling rcv $port, $callback on it.

The block will be called for every message received on the port, with the global variable $SELF set to the port ID. Runtime errors will cause the port to be kiled. The message will be passed as-is, no extra argument (i.e. no port ID) will be passed to the callback.

Register (or replace) callbacks to be called on messages starting with the given tag on the given port (and return the port), or unregister it (when $callback is $undef or missing). There can only be one callback registered for each tag.

The original message will be passed to the callback, after the first element (the tag) has been removed. The callback will use the same environment as the default callback (see above).

Example: create a port and bind receivers on it in one go.

my $port = rcv port,
msg1 => sub { ... },
msg2 => sub { ... },
;

Example: create a port, bind receivers and send it in a message elsewhere in one go:

snd $otherport, reply =>
rcv port,
msg1 => sub { ... },
...
;

Example: temporarily register a rcv callback for a tag matching some port (e.g. for an rpc reply) and unregister it after a message was received.

Monitor the given port and do something when the port is killed or messages to it were lost, and optionally return a guard that can be used to stop monitoring again.

In the first form (callback), the callback is simply called with any number of @reason elements (no @reason means that the port was deleted "normally"). Note also that the callback must never die, so use eval if unsure.

In the second form (another port given), the other port ($rcvport) will be kil'ed with @reason, if a @reason was specified, i.e. on "normal" kils nothing happens, while under all other conditions, the other port is killed with the same reason.

The third form (kill self) is the same as the second form, except that $rvport defaults to $SELF.

In the last form (message), a message of the form @msg, @reason will be snd.

Monitoring-actions are one-shot: once messages are lost (and a monitoring alert was raised), they are removed and will not trigger again.

As a rule of thumb, monitoring requests should always monitor a port from a local port (or callback). The reason is that kill messages might get lost, just like any other message. Another less obvious reason is that even monitoring requests can get lost (for example, when the connection to the other node goes down permanently). When monitoring a port locally these problems do not exist.

mon effectively guarantees that, in the absence of hardware failures, after starting the monitor, either all messages sent to the port will arrive, or the monitoring action will be invoked after possible message loss has been detected. No messages will be lost "in between" (after the first lost message no further messages will be received by the port). After the monitoring action was invoked, further messages might get delivered again.

Inter-host-connection timeouts and monitoring depend on the transport used. The only transport currently implemented is TCP, and AnyEvent::MP relies on TCP to detect node-downs (this can take 10-15 minutes on a non-idle connection, and usually around two hours for idle connections).

This means that monitoring is good for program errors and cleaning up stuff eventually, but they are no replacement for a timeout when you need to ensure some maximum latency.

Creates a port on the node $node (which can also be a port ID, in which case it's the node where that port resides).

The port ID of the newly created port is returned immediately, and it is possible to immediately start sending messages or to monitor the port.

After the port has been created, the init function is called on the remote node, in the same context as a rcv callback. This function must be a fully-qualified function name (e.g. MyApp::Chat::Server::init). To specify a function in the main program, use ::name.

If the function doesn't exist, then the node tries to require the package, then the package above the package and so on (e.g. MyApp::Chat::Server, MyApp::Chat, MyApp) until the function exists or it runs out of package names.

The init function is then called with the newly-created port as context object ($SELF) and the @initdata values as arguments. It must call one of the rcv functions to set callbacks on $SELF, otherwise the port might not get created.

A common idiom is to pass a local port, immediately monitor the spawned port, and in the remote init function, immediately monitor the passed local port. This two-way monitoring ensures that both ports get cleaned up when there is a problem.

spawn guarantees that the $initfunc has no visible effects on the caller before spawn returns (by delaying invocation when spawn is called for the local node).

AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node == aemp node, Erlang process == aemp port), so many of the documents and programming techniques employed by Erlang apply to AnyEvent::MP. Here is a sample:

Erlang relies on special naming and DNS to work everywhere in the same way. AEMP relies on each node somehow knowing its own address(es) (e.g. by configuration or DNS), and possibly the addresses of some seed nodes, but will otherwise discover other nodes (and their IDs) itself.

Erlang has a "remote ports are like local ports" philosophy, AEMP uses "local ports are like remote ports".

The failure modes for local ports are quite different (runtime errors only) then for remote ports - when a local port dies, you know it dies, when a connection to another node dies, you know nothing about the other port.

Erlang pretends remote ports are as reliable as local ports, even when they are not.

AEMP encourages a "treat remote ports differently" philosophy, with local ports being the special case/exception, where transport errors cannot occur.

Erlang uses processes and a mailbox, AEMP does not queue.

Erlang uses processes that selectively receive messages, and therefore needs a queue. AEMP is event based, queuing messages would serve no useful purpose. For the same reason the pattern-matching abilities of AnyEvent::MP are more limited, as there is little need to be able to filter messages without dequeuing them.

(But see Coro::MP for a more Erlang-like process model on top of AEMP).

Erlang sends are synchronous, AEMP sends are asynchronous.

Sending messages in Erlang is synchronous and blocks the process (and so does not need a queue that can overflow). AEMP sends are immediate, connection establishment is handled in the background.

Erlang suffers from silent message loss, AEMP does not.

Erlang implements few guarantees on messages delivery - messages can get lost without any of the processes realising it (i.e. you send messages a, b, and c, and the other side only receives messages a and c).

AEMP guarantees (modulo hardware errors) correct ordering, and the guarantee that after one message is lost, all following ones sent to the same port are lost as well, until monitoring raises an error, so there are no silent "holes" in the message sequence.

Erlang can send messages to the wrong port, AEMP does not.

In Erlang it is quite likely that a node that restarts reuses a process ID known to other nodes for a completely different process, causing messages destined for that process to end up in an unrelated process.

AEMP never reuses port IDs, so old messages or old port IDs floating around in the network will not be sent to an unrelated port.

It has also been carefully designed to be implementable in other languages with a minimum of work while gracefully degrading functionality to make the protocol simple.

AEMP has more flexible monitoring options than Erlang.

In Erlang, you can chose to receive all exit signals as messages or none, there is no in-between, so monitoring single processes is difficult to implement. Monitoring in AEMP is more flexible than in Erlang, as one can choose between automatic kill, exit message or callback on a per-process basis.

Erlang tries to hide remote/local connections, AEMP does not.

Monitoring in Erlang is not an indicator of process death/crashes, in the same way as linking is (except linking is unreliable in Erlang).

In AEMP, you don't "look up" registered port names or send to named ports that might or might not be persistent. Instead, you normally spawn a port on the remote node. The init function monitors you, and you monitor the remote port. Since both monitors are local to the node, they are much more reliable (no need for spawn_link).

This also saves round-trips and avoids sending messages to the wrong port (hard to do in Erlang).

We considered "objects", but found that the actual number of methods that can be called are quite low. Since port and node IDs travel over the network frequently, the serialising/deserialising would add lots of overhead, as well as having to keep a proxy object everywhere.

Strings can easily be printed, easily serialised etc. and need no special procedures to be "valid".

And as a result, a port with just a default receiver consists of a single code reference stored in a global hash - it can't become much cheaper.

In fact, any AnyEvent::MP node will happily accept Storable as framing format, but currently there is no way to make a node use Storable by default (although all nodes will accept it).

The default framing protocol is JSON because a) JSON::XS is many times faster for small messages and b) most importantly, after years of experience we found that object serialisation is causing more problems than it solves: Just like function calls, objects simply do not travel easily over the network, mostly because they will always be a copy, so you always have to re-think your design.