Design And Implementation Of Software System Bus Based On P2P Architecture

In reality, many companies need a reliable and sustainable operation of the system, whether these systems are upgraded, maintenance, reconfiguration, or when an attack can last for more than provide responses to customer requests. Such a system is defined as the Persistence Computing System (PCS). PCS can be connected to the component or application by the SSB (middleware provides asynchronous communication) system to achieve. Perform asynchronous messaging middleware can be called Soft System Bus (SSB). Its main characteristic is that it must be able to save the data, with continuous availability, must support run-time scalability, maintainability, and re-configurability. Although the general requirements of SSB SSB have been identified but not with the design and evaluation of fully realized. Both SMEs and large companies need to PCS system.Some of the existing asynchronous communication middleware in the small and medium enterprises can play the role of SSB in the large enterprise applications, but these asynchronous communication middleware is not very appropriate. Large main objective of the PCS system is that even in the middleware node (ie broker) or one or more sites of application/component failure or a disaster because they are upgrading or maintenance or reconfiguration, the user can also get system services.This article explores is the SSB in the large enterprise systems design and implementation.In these traditional middleware is the main problem found in the network section (broker) is essentially static. In this paper, the network node becomes dynamic and the application does not rely on a single node or a site to solve this problem, which means that applications can connect to any node. Therefore, if a node fails, or if it is disconnected during the upgrade or maintenance, connection to its application will also be connected to another node. In this paper, a P2P-based architecture of SSB to realize this. As the P2P network has a good dynamic nature, if a node (broker) fails, its neighbors (broker) will take over its services. Therefore, applications can access services at any time. This design of SSB can not immediately pass on a message to the target application, to provide for the message saving. SSB is designed to be based on the P2P network nodes, it has a self-management capabilities so that it requires minimal administrative overhead. In addition, the structure of the deployment of P2P network does not require each site to install the node (broker), the cost of deployment compared to other middleware is very small.This article uses the P2P network and the traditional use of different methods is not the same. In the SSB in, P2P networks for applications in providing a reliable point to point communication channels, rather than for shared storage or provide a multi-cast communication channel. In addition, unlike traditional Internet-scale P2P networks, we build P2P networks in the enterprise, so that P2P node/broker will be very safe and rarely fails.In order to evaluate this design, a PCS system in a simulated environment is established. The PCS system has an analog realization of our proposed protocol middleware (SSB). By using the simulator shows that even in the node or application in case of failure, PCS does not have any long-term non-service (it is a continuous uninterrupted operation). Middleware with Microsoft Message Queuing (MSMQ) comparative studies show that this method can reduce the communication overhead, and we have a lot of middleware nodes and nodes in the distributed network of large geographic range of deployment costs when it is deployed on is low. For example, in the deployment of a global enterprise. This article also shows that the deployment cost and administrative overhead, our middleware is superior to other messaging middleware. Therefore, this middleware compared to other middleware is more suitable for large-scale PCS systems SSB.