GitHub user pjfanning edited a comment on the discussion: Akka <-> Pekko wire
compatibility
Have a look in the `remote` src/main directory. There are only 2 places where
you will find the string `"pekko"` (with the double quotes). Start with these.
Any solution that we would accept as a Pekko patch would probably require:
* that the URL schemes are configurable (reference.conf)
* that the Pekko nodes will form clusters with nodes using either `pekko:` or
`akka:`
* this allows you to start by configuring all the Pekko nodes to use
`akka:` addresses so that they can fool real Akka nodes into interacting with
them
* once you have managed to replace all the real Akka nodes with Pekko nodes
pretending to be Akka nodes, then you can start replacing some of these Pekko
nodes with Pekko nodes that are using `pekko:` addresses - until all the nodes
are changed to use `pekko:` addresses
* we probably don't want to be forced to allow the `pekko:` scheme to be
configurable in Pekko 2.0.0 so we need a way to allow users to migrate away
from having Pekko nodes that pretend to be Akka nodes
* we would need to have good test coverage with mixed nodes
Anyone is welcome to fork Pekko and modify their forks to go back to using
`akka:` addresses. There is a higher bar for what we would merge into Pekko
itself.
GitHub link:
https://github.com/apache/incubator-pekko/discussions/586#discussioncomment-6806861
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
