Messaging links client applications to each other and to Enterprise applications, services, and data. Messaging can take various forms, whether a plain socket-based application, Web Services, or a more sophisticated store and forward transaction messaging capability that supports connected as well as disconnected usage.
When choosing a form of messaging, you should consider the following requirements in the design of your end-to-end applications:
- online vs. offline operation
- security, including message confidentiality, non-repudiation, and authentication
- synchronous versus asynchronous messaging
- once-only assured transactions
- configuration of the messaging solution
Web Services support secure, online, synchronous access to information; however, an online connection must be active between the Web Services consumer and provider to access information across the network. Security features include message confidentiality, integrity, and authentication.
Certain nodes in the end-to-end system might not be able to manage or commit transactions because these nodes might not have transaction coordination and, therefore, do not have the master copy of all of the data.
Micro broker provides transactional messaging capabilities with support for:
- online and offline operations
- synchronous and asynchronous messaging
- publish subscribe and point-to-point messaging
- assured delivery of messages
- connectivity to backend messaging servers including WebSphere MQ
- security features like encryption, authentication and authorization
- intra-process, inter-process and inter-node communication
It is a convenient mechanism for applications requiring decoupled communication either locally or with enterprise systems.
Parent topic: Application design considerations: XPD621