Using akka-remoting / akka-cluster for communication creates very tight
coupling between components. If these components are being developed by
separate teams, a lot of deliberate coordination work will be needed.
I think that in modern microsevice-oriented environments it's more typical
to to
Suyog,
My suggestion is to move these messages to a shared library and let it be
your "executable documentation". If anyone needs to send messages to an
actor system of another team, just import the library of this team and then
you can figure out what are the actors and what case classes you can
Hi Allan,
Did you mean that, if two different teams working on different actor
systems, which needs to communicate with each other
In this case, one team should look into others code to check what actors
are there and what messages it consumes?
Have you tried something like Java Docs with
Hi,
See this snippet of code:
https://gist.github.com/douglaz/e06c1b6dbe95a14407866165af50ad1e
Look the companion object. It's not what you want (documentation), but just
an example of a convention that helps figure out what messages an Akka
actor receives and what kind of data it keeps.
[]'s
ᐧ
Hi,
Is there any recommended practice to define contract between multiple actor
systems?
In short, how one actor system should release document of what all actors
it contains and what kind of messages each actor can expect? Something
similar to swagger docs in REST API world.
Regards,
Suyog
