a few more things when reviewing replicated event sourcing (#29461)
This commit is contained in:
parent
f41f093372
commit
fb5f5dc145
9 changed files with 43 additions and 56 deletions
|
|
@ -21,12 +21,10 @@ With a [Lightbend Platform Subscription](https://www.lightbend.com/lightbend-sub
|
|||
* [Configuration Checker](https://doc.akka.io/docs/akka-enhancements/current/config-checker.html) — Checks for potential configuration issues and logs suggestions.
|
||||
* [Diagnostics Recorder](https://doc.akka.io/docs/akka-enhancements/current/diagnostics-recorder.html) — Captures configuration and system information in a format that makes it easy to troubleshoot issues during development and production.
|
||||
* [Thread Starvation Detector](https://doc.akka.io/docs/akka-enhancements/current/starvation-detector.html) — Monitors an Akka system dispatcher and logs warnings if it becomes unresponsive.
|
||||
* [Kubernetes Lease](https://doc.akka.io/docs/akka-enhancements/current/kubernetes-lease.html) — Monitors an Akka system dispatcher and logs warnings if it becomes unresponsive.
|
||||
* [Fast Failover](https://doc.akka.io/docs/akka-enhancements/current/fast-failover.html) — Fast failover for Cluster Sharding.
|
||||
|
||||
[Akka Persistence Enhancements](https://doc.akka.io/docs/akka-enhancements/current/akka-persistence-enhancements.html):
|
||||
|
||||
* [Multi-DC Persistence](https://doc.akka.io/docs/akka-enhancements/current/persistence-dc/index.html) — For active-active persistent entities across multiple data centers.
|
||||
* [GDPR for Akka Persistence](https://doc.akka.io/docs/akka-enhancements/current/gdpr/index.html) — Data shredding can be used to forget information in events.
|
||||
|
||||
This page does not list all available modules, but overviews the main functionality and gives you an idea of the level of sophistication you can reach when you start building systems on top of Akka.
|
||||
|
|
|
|||
|
|
@ -657,9 +657,9 @@ cluster and address them by id.
|
|||
Akka Persistence is based on the single-writer principle. For a particular `PersistenceId` only one `EventSourcedBehavior`
|
||||
instance should be active at one time. If multiple instances were to persist events at the same time, the events would
|
||||
be interleaved and might not be interpreted correctly on replay. Cluster Sharding ensures that there is only one
|
||||
active entity (`EventSourcedBehavior`) for each id within a data center. Lightbend's
|
||||
[Multi-DC Persistence](https://doc.akka.io/docs/akka-enhancements/current/persistence-dc/index.html)
|
||||
supports active-active persistent entities across data centers.
|
||||
active entity (`EventSourcedBehavior`) for each id within a data center.
|
||||
@ref:[Replicated Event Sourcing](replicated-eventsourcing.md) supports active-active persistent entities across
|
||||
data centers.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
|
@ -684,5 +684,5 @@ from the events, or publish the events to other services.
|
|||
|
||||
@java[@extref[Multi-DC Persistence example project](samples:akka-samples-persistence-dc-java)]
|
||||
@scala[@extref[Multi-DC Persistence example project](samples:akka-samples-persistence-dc-scala)]
|
||||
illustrates how to use Lightbend's [Multi-DC Persistence](https://doc.akka.io/docs/akka-enhancements/current/persistence-dc/index.html)
|
||||
with active-active persistent entities across data centers.
|
||||
illustrates how to use @ref:[Replicated Event Sourcing](replicated-eventsourcing.md) that supports
|
||||
active-active persistent entities across data centers.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue