From 904705b3dfc28f8ecc0bef3e4e7f7ff8dc26c589 Mon Sep 17 00:00:00 2001 From: PJ Fanning Date: Wed, 8 Mar 2023 13:07:44 +0100 Subject: [PATCH] Update migration-guides.md --- docs/src/main/paradox/project/migration-guides.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/src/main/paradox/project/migration-guides.md b/docs/src/main/paradox/project/migration-guides.md index 029ad79415..59164f9a4d 100644 --- a/docs/src/main/paradox/project/migration-guides.md +++ b/docs/src/main/paradox/project/migration-guides.md @@ -16,11 +16,15 @@ This is just stub documentation. It will be improved. * Pekko packages start with "org.apache.pekko" instead of "akka" - e.g. `import org.apache.pekko.actor` instead of `import akka.actor` * Where class names have "Akka" in the name, the Pekko ones have "Pekko" - e.g. PekkoException instead of AkkaException * Configs in `application.conf` use "pekko" prefix instead of "akka" +* We have changed the default ports used by the pekko-remote module. +* With @ref:[Classic Remoting](../remoting.md), Akka defaults to 2552, while Pekko defaults to 7355. +* With @ref:[Artery Remoting](../remoting-artery.md), Akka defaults to 25520, while Pekko defaults to 17355. We are still investigating the effects of how the package name changes affect the @ref:[Persistence](../persistence.md) and @ref:[Cluster](../cluster-usage.md) modules. -Data persisted with "akka-persistence" may not yet be usable with "pekko-persistence" (or vice versa). -Akka and Pekko nodes may not be able to form a cluster or messages may not be recognised if passed between nodes -of different types. + +It appears that data persisted with "akka-persistence" is usable with "pekko-persistence" (and vice versa). + +We currently do not expect that Akka and Pekko nodes will be able to form a cluster. We may be able to provide [Scalafix](https://scalacenter.github.io/scalafix/) scripts to help with migrations.