Abstract: An exemplary method includes a broker-based messaging system detecting a request provided by a software application for the software application to connect to any one of a plurality of brokers included in a cluster of brokers, dynamically identifying, in response to the request and in accordance with a connection distribution heuristic, a broker included in the cluster of brokers and that is available for connection to the software application, and attempting to establish a connection between the software application and the broker. Corresponding methods and systems are also disclosed.

Abstract: An exemplary method includes a message broker subsystem receiving a message intended for delivery to a recipient software application instance, determining that the recipient software application instance is included in a plurality of functionally equivalent software application instances that are registered with a global directory service subsystem that is communicatively coupled to the message broker subsystem, automatically selecting a software application instance from the plurality of software application instances for receipt of the message in accordance with a load balancing heuristic, and attempting to deliver the message to the selected software application instance. Corresponding methods and systems are also described.

Abstract: An exemplary method includes a message broker subsystem 1) attempting to deliver one or more messages intended for a recipient software application to the recipient software application, 2) determining that the recipient software application is in a fault state after failing to deliver the one or more messages to the recipient software application, 3) automatically performing a fail-over process on one or more other messages intended for the recipient software application in response to the determination that the recipient software application is in the fault state, and 4) continuing to attempt to deliver a message selected from the one or more messages to the recipient software application while automatically performing the fail-over process on the one or more other messages. Corresponding methods and systems are also disclosed.

Abstract: An exemplary method includes a global directory service subsystem receiving a request for a software application to be temporarily registered with a message broker in accordance with a universal registration heuristic, authorizing, in response to the request and in accordance with permission information associated with the software application and maintained by the global directory service subsystem, the software application to be temporarily registered with the message broker; and dynamically updating, in response to the authorizing, software application registration data maintained by the global directory service subsystem to indicate that the software application is temporarily registered with the message broker. Corresponding methods and systems are also described.

Abstract: An exemplary method includes a broker-based messaging system detecting a request provided by a software application for the software application to connect to any one of a plurality of brokers included in a cluster of brokers, dynamically identifying, in response to the request and in accordance with a connection distribution heuristic, a broker included in the cluster of brokers and that is available for connection to the software application, and attempting to establish a connection between the software application and the broker. Corresponding methods and systems are also disclosed.

Abstract: An exemplary method includes a message broker subsystem 1) attempting to deliver one or more messages intended for a recipient software application to the recipient software application, 2) determining that the recipient software application is in a fault state after failing to deliver the one or more messages to the recipient software application, 3) automatically performing a fail-over process on one or more other messages intended for the recipient software application in response to the determination that the recipient software application is in the fault state, and 4) continuing to attempt to deliver a message selected from the one or more messages to the recipient software application while automatically performing the fail-over process on the one or more other messages. Corresponding methods and systems are also disclosed.

Abstract: An exemplary method includes a global directory service subsystem receiving a request for a software application to be temporarily registered with a message broker in accordance with a universal registration heuristic, authorizing, in response to the request and in accordance with permission information associated with the software application and maintained by the global directory service subsystem, the software application to be temporarily registered with the message broker; and dynamically updating, in response to the authorizing, software application registration data maintained by the global directory service subsystem to indicate that the software application is temporarily registered with the message broker. Corresponding methods and systems are also described.

Abstract: An exemplary method includes a message broker subsystem receiving a message intended for delivery to a recipient software application instance, determining that the recipient software application instance is included in a plurality of functionally equivalent software application instances that are registered with a global directory service subsystem that is communicatively coupled to the message broker subsystem, automatically selecting a software application instance from the plurality of software application instances for receipt of the message in accordance with a load balancing heuristic, and attempting to deliver the message to the selected software application instance. Corresponding methods and systems are also described.

Abstract: An exemplary method includes attempting, by a message broker subsystem, to deliver one or more messages intended for a recipient software application to the recipient software application during a predetermined fault interval, determining, by the message broker subsystem, that the recipient software application is in a fault state after failing to deliver the one or more messages to the recipient software application during the predetermined fault interval, and automatically performing, by the message broker subsystem, a fail-over process on one or more other messages intended for the recipient software application in response to the determination that the recipient software application is in the fault state. Corresponding methods and systems are also disclosed.

Abstract: An exemplary method includes attempting, by a message broker subsystem, to deliver one or more messages intended for a recipient software application to the recipient software application during a predetermined fault interval, determining, by the message broker subsystem, that the recipient software application is in a fault state after failing to deliver the one or more messages to the recipient software application during the predetermined fault interval, and automatically performing, by the message broker subsystem, a fail-over process on one or more other messages intended for the recipient software application in response to the determination that the recipient software application is in the fault state. Corresponding methods and systems are also disclosed.