=doc #3883 Eventsourced to Akka Persistence comparison/migration
This commit is contained in:
parent
24688cc864
commit
dc3164d1b1
4 changed files with 241 additions and 3 deletions
|
|
@ -21,7 +21,8 @@ communication channels with at-least-once message delivery semantics.
|
|||
contents of the ``akka.persistence`` package.
|
||||
|
||||
Akka persistence is inspired by and the official replacement of the `eventsourced`_ library. It follows the same
|
||||
concepts and architecture of `eventsourced`_ but significantly differs on API and implementation level.
|
||||
concepts and architecture of `eventsourced`_ but significantly differs on API and implementation level. See also
|
||||
:ref:`migration-eventsourced-2.3`
|
||||
|
||||
.. _eventsourced: https://github.com/eligosource/eventsourced
|
||||
|
||||
|
|
@ -81,6 +82,8 @@ A ``Processor`` itself is an ``Actor`` and can therefore be instantiated with ``
|
|||
|
||||
.. includecode:: code/docs/persistence/PersistenceDocSpec.scala#usage
|
||||
|
||||
.. _recovery:
|
||||
|
||||
Recovery
|
||||
--------
|
||||
|
||||
|
|
@ -295,6 +298,8 @@ If an application wants to have more control how sequence numbers are assigned t
|
|||
application-specific sequence number generator and include the generated sequence numbers into the ``payload``
|
||||
of ``Persistent`` messages.
|
||||
|
||||
.. _persistent-channels:
|
||||
|
||||
Persistent channels
|
||||
-------------------
|
||||
|
||||
|
|
@ -333,6 +338,8 @@ creating the channel with the ``replyPersistent`` configuration parameter set to
|
|||
With this setting, either the successfully persisted message is replied to the sender or a ``PersistenceFailure``
|
||||
message. In case the latter case, the sender should re-send the message.
|
||||
|
||||
.. _processor-identifiers:
|
||||
|
||||
Identifiers
|
||||
-----------
|
||||
|
||||
|
|
@ -344,6 +351,8 @@ a channel identifier, it should be provided as argument ``Channel.props(String)`
|
|||
|
||||
.. includecode:: code/docs/persistence/PersistenceDocSpec.scala#channel-id-override
|
||||
|
||||
.. _persistent-messages:
|
||||
|
||||
Persistent messages
|
||||
===================
|
||||
|
||||
|
|
@ -490,6 +499,8 @@ In larger integration scenarios, channel destinations may be actors that submit
|
|||
message broker, for example. After having successfully submitted an event, they should call ``confirm()`` on the
|
||||
received ``ConfirmablePersistent`` message.
|
||||
|
||||
.. _batch-writes:
|
||||
|
||||
Batch writes
|
||||
============
|
||||
|
||||
|
|
@ -520,6 +531,8 @@ Confirmation and deletion operations performed by :ref:`channels` are also batch
|
|||
and deletion batch sizes are configurable with ``akka.persistence.journal.max-confirmation-batch-size`` and
|
||||
``akka.persistence.journal.max-deletion-batch-size``, respectively.
|
||||
|
||||
.. _storage-plugins:
|
||||
|
||||
Storage plugins
|
||||
===============
|
||||
|
||||
|
|
@ -531,6 +544,8 @@ imports:
|
|||
|
||||
.. includecode:: code/docs/persistence/PersistencePluginDocSpec.scala#plugin-imports
|
||||
|
||||
.. _journal-plugin-api:
|
||||
|
||||
Journal plugin API
|
||||
------------------
|
||||
|
||||
|
|
@ -571,6 +586,8 @@ A snapshot store plugin can be activated with the following minimal configuratio
|
|||
The specified plugin ``class`` must have a no-arg constructor. The ``plugin-dispatcher`` is the dispatcher
|
||||
used for the plugin actor. If not specified, it defaults to ``akka.persistence.dispatchers.default-plugin-dispatcher``.
|
||||
|
||||
.. _pre-packaged-plugins:
|
||||
|
||||
Pre-packaged plugins
|
||||
====================
|
||||
|
||||
|
|
@ -635,6 +652,8 @@ directory. This can be changed by configuration where the specified path can be
|
|||
|
||||
.. includecode:: code/docs/persistence/PersistencePluginDocSpec.scala#snapshot-config
|
||||
|
||||
.. _custom-serialization:
|
||||
|
||||
Custom serialization
|
||||
====================
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue