We have a parent
about many nodes
Keeps the information. Each node has a different VM example, which performs various functions. The root
is like a dashboard for all nodes.
original
is required:
- Send some topical configuration
node
- Change in
node
- Get some data from
. Node
I think the node
is not as far as possible as possible. Each node
works as a web server, they can sometimes get large traffic.
Parents
and nodes
?
I was thinking of using files for communication, so set the file with a command on original
a node
file You can do the system, and then there is a DIRE viewer who reads for such files.
Or there are some event-bus / message-queues in the background, but they are using sockets, so in case of a node high traffic
parent
Message can not be responsive. Or maybe I worry too much?
Edit
Is there an Event / Message-Bus that provides direct communication between channels to save time for broadcast? In my example, communication is always between parents
and single children
, there is no need to broadcast. So we can email some messages like;)
Edit # 2 - About Communications and Traffic
is a original
(or a cluster Examples of a parent who represents one) The number of children
is not determined, it can be anyone; The goal will be as much as possible, as long as the system works fine. Communication is:
-
Command (
parent
->child
) Orders, usually started by administrator (Such as "restart", "upload", "reload configuration"). It goes directly to the specificchildren
. -
Runtime statistics (each
child
->parent
) eachchild
your health ( Heart beat) and some minor data aboutguardian
. This should not be a real time communication, until the message is moved 10 seconds. -
Runtime log (each
child
->parent
) Important logs about traffic and usage. It can be high-volume data because it is important to measure each node, if the calculation exceeds some limit, then we should know about it. Again, not real time, but we need urgent warnings on high calculations. / P>
There is no need for normal transmission (since children
s are not aware of other babies), this is a more direct message.
I advise you to use, because you have the necessary methods to communicate between the nodes , The class you want to communicate with is extending into the remote
interface.
You have to use rmiregistry
at the beginning of communication, but then it was won
Updates : if you have If there is a "central" node for delivering the reference / message, then it will not be needed again. I am not advanced to answer your last question, but this link can help you with what you want:
1.-
2.-
No comments:
Post a Comment