我想设计一个核心和核心之上的多个模块的应用程序。核心将负责从网络接收消息，解析传入的消息并将消息分发到注册的模块。
有多种类型的消息，一些模块可能有兴趣只接收其中的一些类型。模块可以并行执行，也可以顺序执行（例如，当模块以明确定义的执行顺序相互依赖时）。
此外，即使核心已启动，如果模块可以部署/取消部署，那就太好了。
这对我来说是全新的，我曾经编写模块化应用程序，但多个部分是静态连接的。
对于这样的设计，我应该采取哪个方向（即框架、模式……）？我不知道它是否与我的问题有关，但我确切地说我将使用 Java。
谢谢
You has a very good approach at the architecture level. But it will be beneficial only when your application layers/tire will be at separate instance, so that you can shut down one module/server and while other part will still be running. Point is will you run the modules on separate instances?
Secondly, I would like to suggest you to build the application core architecture using Web-Service either REST/SOAP as it will automatic achieve your thought that follows Service Oriented Architecture (SOA). That will be producer - consumer relation and you can run on separate instance. And while deploying/undeploying you can still run the services part to support other client instances.
Using Web service will also provide you a global information exchange system that will likely to communicate with several application views/front end.