raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 10

Remove ApiMayChange for Replicated Event Sourcing, #30346 (#30347)

Browse source
This commit is contained in:
Patrik Nordwall 2021-06-28 17:11:55 +02:00 • committed by GitHub
parent bbae718ef7
commit 8573c70883
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
12 changed files with 36 additions and 48 deletions
Download patch file Download diff file Expand all files Collapse all files

1
akka-docs/src/main/paradox/common/may-change.md
View file

@ -31,6 +31,5 @@ These are the current complete modules marked as **may change**:
* @ref:[Multi Node Testing](../multi-node-testing.md)
* @ref:[Reliable Delivery](../typed/reliable-delivery.md)
* @ref:[Sharded Daemon Process](../typed/cluster-sharded-daemon-process.md)
* @ref:[Replicated Event Sourcing](../typed/replicated-eventsourcing.md)

8
akka-docs/src/main/paradox/typed/replicated-eventsourcing.md
View file

@ -1,13 +1,5 @@
# Replicated Event Sourcing
@@@ warning
This module is marked as @ref:[may change](../common/may-change.md) because it is a new feature that
needs feedback from real usage before finalizing the API. This means that API or semantics can change without
warning or deprecation period. It is also not recommended to use this module in production just yet.
@@@
@ref[Event Sourcing](./persistence.md) with `EventSourcedBehavior`s is based on the single writer principle, which means that there can only be one active instance of a `EventSourcedBehavior`
with a given `persistenceId`. Otherwise, multiple instances would store interleaving events based on different states, and when these events would later be replayed it would not be possible to reconstruct the correct state.