Akka/Scala example source code file (agents.rst)

This example Akka source code file (agents.rst) is included in my "Source Code Warehouse" project. The intent of this project is to help you more easily find Akka and Scala source code examples by using tags.

All credit for the original source code belongs to akka.io; I'm just trying to make examples easier to find. (For my Scala work, see my Scala examples and tutorials.)

Akka tags/keywords

actors, agent, agent's, agents, future, futures, reading, the, there, you

The agents.rst Akka example source code

.. _agents-scala:

########
 Agents
########

Agents in Akka are inspired by `agents in Clojure`_.

.. _agents in Clojure: http://clojure.org/agents

Agents provide asynchronous change of individual locations. Agents are bound to
a single storage location for their lifetime, and only allow mutation of that
location (to a new state) to occur as a result of an action. Update actions are
functions that are asynchronously applied to the Agent's state and whose return
value becomes the Agent's new state. The state of an Agent should be immutable.

While updates to Agents are asynchronous, the state of an Agent is always
immediately available for reading by any thread (using ``get`` or ``apply``)
without any messages.

Agents are reactive. The update actions of all Agents get interleaved amongst
threads in an ``ExecutionContext``. At any point in time, at most one ``send`` action for
each Agent is being executed. Actions dispatched to an agent from another thread
will occur in the order they were sent, potentially interleaved with actions
dispatched to the same agent from other threads.

.. note::

  Agents are local to the node on which they are created. This implies that you
  should generally not include them in messages that may be passed to remote Actors
  or as constructor parameters for remote Actors; those remote Actors will not be able to
  read or update the Agent.
 
Creating Agents
===============

Agents are created by invoking ``Agent(value)`` passing in the Agent's initial
value and providing an implicit ``ExecutionContext`` to be used for it, for these
examples we're going to use the default global one, but YMMV:

.. includecode:: code/docs/agent/AgentDocSpec.scala#create

Reading an Agent's value
========================

Agents can be dereferenced (you can get an Agent's value) by invoking the Agent
with parentheses like this:

.. includecode:: code/docs/agent/AgentDocSpec.scala#read-apply

Or by using the get method:

.. includecode:: code/docs/agent/AgentDocSpec.scala#read-get

Reading an Agent's current value does not involve any message passing and
happens immediately. So while updates to an Agent are asynchronous, reading the
state of an Agent is synchronous.

Updating Agents (send & alter)
==============================

You update an Agent by sending a function that transforms the current value or
by sending just a new value. The Agent will apply the new value or function
atomically and asynchronously. The update is done in a fire-forget manner and
you are only guaranteed that it will be applied. There is no guarantee of when
the update will be applied but dispatches to an Agent from a single thread will
occur in order. You apply a value or a function by invoking the ``send``
function.

.. includecode:: code/docs/agent/AgentDocSpec.scala#send

You can also dispatch a function to update the internal state but on its own
thread. This does not use the reactive thread pool and can be used for
long-running or blocking operations. You do this with the ``sendOff``
method. Dispatches using either ``sendOff`` or ``send`` will still be executed
in order.

.. includecode:: code/docs/agent/AgentDocSpec.scala#send-off

All ``send`` methods also have a corresponding ``alter`` method that returns a ``Future``.
See :ref:`futures-scala` for more information on ``Futures``.

.. includecode:: code/docs/agent/AgentDocSpec.scala#alter

.. includecode:: code/docs/agent/AgentDocSpec.scala#alter-off

Awaiting an Agent's value
=========================

You can also get a ``Future`` to the Agents value, that will be completed after the
currently queued updates have completed:

.. includecode:: code/docs/agent/AgentDocSpec.scala#read-future

See :ref:`futures-scala` for more information on ``Futures``.

Monadic usage
=============

Agents are also monadic, allowing you to compose operations using
for-comprehensions. In monadic usage, new Agents are created leaving the
original Agents untouched. So the old values (Agents) are still available
as-is. They are so-called 'persistent'.

Example of monadic usage:

.. includecode:: code/docs/agent/AgentDocSpec.scala#monadic-example

Configuration
=============

There are several configuration properties for the agents module, please refer
to the :ref:`reference configuration <config-akka-agent>`.

Deprecated Transactional Agents
===============================

Agents participating in enclosing STM transaction is a deprecated feature in 2.3.

If an Agent is used within an enclosing transaction, then it will participate in
that transaction. If you send to an Agent within a transaction then the dispatch
to the Agent will be held until that transaction commits, and discarded if the
transaction is aborted. Here's an example:

.. includecode:: code/docs/agent/AgentDocSpec.scala#transfer-example