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

temporarily remove refs to platform guide (#280)

Browse source 
Update persistence-testing.md
This commit is contained in:
PJ Fanning 2023-04-11 20:29:42 +02:00 • committed by GitHub
parent 2c4d0ee02d
commit 658e4bc4b0
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
7 changed files with 3 additions and 30 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/src/main/paradox/persistence-query.md
View file

@ -33,9 +33,6 @@ recommend (in the spirit of CQRS) of splitting up the write/read sides into sepa
For a similar implementation of query interface to @ref:[Durable State Behaviors](typed/durable-state/persistence.md)
please refer to @ref:[Persistence Query using Durable State](durable-state/persistence-query.md).
The @extref[Microservices with Pekko tutorial](platform-guide:microservices-tutorial/) explains how to
implement an Event Sourced CQRS application with Pekko Persistence and Pekko Projections.
## Design overview
Pekko persistence query is purposely designed to be a very loosely specified API.
@ -333,8 +330,3 @@ resilience is important so that if a node crashes the persistent queries are qui
resume operations @ref:[Cluster Sharding](cluster-sharding.md) together with event tagging is an excellent fit to
shard events over a cluster.
## Example project
The @extref[Microservices with Pekko tutorial](platform-guide:microservices-tutorial/) explains how to
use Event Sourcing and Projections together. The events are tagged to be consumed by even processors to build
other representations from the events, or publish the events to other services.

7
docs/src/main/paradox/project/examples.md
View file

@ -50,13 +50,6 @@ This project contains a KillrWeather sample illustrating how to use Cluster Shar
This project contains a Shopping Cart sample illustrating how to use Pekko Persistence.
## CQRS
The @extref[Microservices with Pekko tutorial](platform-guide:microservices-tutorial/) contains a
Shopping Cart sample illustrating how to use Event Sourcing and Projections together. The events are
tagged to be consumed by even processors to build other representations from the events, or publish the events
to other services.
## Replicated Event Sourcing
@java[@extref[Multi-DC Persistence example project](samples:pekko-samples-persistence-dc-java)]

2
docs/src/main/paradox/typed/choosing-cluster.md
View file

@ -17,8 +17,6 @@ In a microservices architecture, you should consider communication within a serv
In general we recommend against using Pekko Cluster and actor messaging between _different_ services because that
would result in a too tight code coupling between the services and difficulties deploying these independent of
each other, which is one of the main reasons for using a microservices architecture.
See the discussion on @extref[Internal and External Communication](platform-guide:concepts/internal-and-external-communication.html)
for some background on this.
Nodes of a single service (collectively called a cluster) require less decoupling. They share the same code and
are deployed together, as a set, by a single team or individual. There might be two versions running concurrently

5
docs/src/main/paradox/typed/cqrs.md
View file

@ -1,6 +1,5 @@
# CQRS
@ref:[EventSourcedBehavior](persistence.md)s along with [Pekko Projections]($pekko.doc.dns$/docs/pekko-projection/current/)
can be used to implement Command Query Responsibility Segregation (CQRS). The @extref[Microservices with Pekko tutorial](platform-guide:microservices-tutorial/)
explains how to use Event Sourcing and Projections together. For implementing CQRS using @ref:[DurableStateBehavior](durable-state/persistence.md), please take a look at the corresponding @ref:[CQRS](durable-state/cqrs.md) documentation.
can be used to implement Command Query Responsibility Segregation (CQRS).
For implementing CQRS using @ref:[DurableStateBehavior](durable-state/persistence.md), please take a look at the corresponding @ref:[CQRS](durable-state/cqrs.md) documentation.

1
docs/src/main/paradox/typed/guide/tutorial_5.md
View file

@ -233,5 +233,4 @@ To continue your journey with Pekko, we recommend:
To get from this guide to a complete application you would likely need to provide either an UI or an API. For this we recommend that you look at the following technologies and see what fits you:
* @extref[Microservices with Pekko tutorial](platform-guide:microservices-tutorial/) illustrates how to implement an Event Sourced CQRS application with Pekko Persistence and Pekko Projections
* [Pekko HTTP]($pekko.doc.dns$/docs/pekko-http/current/introduction.html) is a HTTP server and client library, making it possible to publish and consume HTTP endpoints

2
docs/src/main/paradox/typed/persistence-testing.md
View file

@ -189,8 +189,6 @@ For tests that involve more than one Cluster node you have to use another journa
While it's possible to use the @ref:[Persistence Plugin Proxy](../persistence-plugins.md#persistence-plugin-proxy)
it's often better and more realistic to use a real database.
The @ref:[CQRS example](../project/examples.md#cqrs) includes tests that are using Pekko Persistence Cassandra.
### Plugin initialization
Some Persistence plugins create tables automatically, but has the limitation that it can't be done concurrently

8
docs/src/main/paradox/typed/persistence.md
View file

@ -39,9 +39,7 @@ or starting from a checkpoint in a snapshot, which can dramatically reduce recov
Pekko Persistence also supports @ref:[Durable State Behaviors](durable-state/persistence.md), which is based on
persistence of the latest state of the actor. In this implementation, the _latest_ state is persisted, instead of events.
Hence this is more similar to CRUD based applications.
The @extref[Microservices with Pekko tutorial](platform-guide:microservices-tutorial/) illustrates how to implement an Event Sourced CQRS application with Pekko Persistence and Pekko Projections.
Hence, this is more similar to CRUD based applications.
@@@ note
@ -681,10 +679,6 @@ reference documentation of the chosen plugin.
is an example project that can be downloaded, and with instructions of how to run.
This project contains a Shopping Cart sample illustrating how to use Pekko Persistence.
The Shopping Cart sample is expanded further in the @extref[Microservices with Pekko tutorial](platform-guide:microservices-tutorial/).
In that sample the events are tagged to be consumed by even processors to build other representations
from the events, or publish the events to other services.
@java[@extref[Multi-DC Persistence example project](samples:pekko-samples-persistence-dc-java)]
@scala[@extref[Multi-DC Persistence example project](samples:pekko-samples-persistence-dc-scala)]
illustrates how to use @ref:[Replicated Event Sourcing](replicated-eventsourcing.md) that supports