分布式应用架构
我们正在构建一个应用程序，该应用程序将在许多站点上安装客户端。每个客户端都独立工作，拥有自己的数据库和工作流程。然而，每个客户端必须向安装在中央位置的主应用程序提交一些数据。位于中央位置的应用程序必须从分布式单元接收更新（例如库存水平）。所有应用程序都是用Java 完成的。将更新从分布式单元发送到中央应用程序的最佳方式/技术是什么？ JMS、jdbc、...？
We are building an application that will have clients installed in many sites. Each client work on its own, has its own database and workflows. However, each client has to submit some data to the main application installed at a central position. The application at a central location must receive updates (e.g stock levels) from the distributed units. All applications are done in Java. Which is the best way/technology of sending the updates from the distributed units to the central application? JMS, jdbc, ...?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我将假设客户端站点的服务器具有网络访问权限，并且您可以配置中央服务器，以便其他客户端可以连接到它。这可以通过互联网或内部 WAN 进行。
在这种情况下，只需找到一种机制来提交一些格式正确的数据，这些数据由中央服务器接收和处理。这为您提供了大量选项，我将仅列出其中几个：
所有这些都可以工作，所以这实际上取决于确定哪一个最适合您的架构。我怀疑最简单的是 Kryonet，最全面的可能是完整的 JBoss ESB/应用程序服务器堆栈。
I'm going to assume that the servers at client sites have network access, and that you are able to configure the central server so that other clients can connect to it. This could either be over the internet or an internal WAN.
In this case, it's simply a case of finding a mechanism to submit some correctly formatted data, which is received and handled by the central server. This gives you a large number of options, I'm going to list just a few:
All of these will work, so it really depends on working out which is the best fit for your architecture. I suspect the simplest would be something like Kryonet, the most comprehensive would probably be something like a full JBoss ESB/application server stack.