I want to design an app with a core and several modules at the top of the core. To parse incoming messages of the core and deliver messages to the registered module, it will be the responsibility of receiving messages from the network.
There are many types of messages, some modules can only be interested in getting some types of modules can execute in parallel, or they can execute sequentially (for example, when the module Are dependent on each other with a well-defined sequence of execution).
In addition, it would be great if the module can also be deployed / undeployed core up.
This is completely new to me, I wanted to write modular applications, but many parts were wired steadily.
Which direction (i.e. outline, pattern ...) should I take for such a design? I do not know that this is relevant to my question, but I'm right that I will use Java.
Thanks
-
Your
architecture level < There is a great way to / code> but it will be beneficial only when your application will be
layers / tires on a different example, so that you can close a
module / server And other parts are still running. Do you run the module on different instances?
Secondly, I would suggest to you that you have created the application core architecture / because it will automatically get your idea as follows, it is
manufacturer-consumer will belong and you can run on different examples. And when you deploy / deploy, you can still run part of the services to support other client instances.
By using the web service, you will also get a global information exchange system which can be seen in many app views / front end.
Comments
Post a Comment