Developers deploying Red Hat AMQ on Red Hat OpenShift often wonder how to connect external clients to AMQ Broker using the Transport Layer Security (TLS) protocol, which is an improved successor to the Secure Sockets Layer (SSL) protocol.
Continue reading Connecting external clients to Red Hat AMQ Broker on Red Hat OpenShift
Red Hat JBoss AMQ Interconnect provides flexible routing of messages between AMQP-enabled endpoints, including clients, brokers, and standalone services. With a single connection to a network of AMQ Interconnect routers, a client can exchange messages with any other endpoint connected to the network.
AMQ Interconnect can create various topologies to manage a high volume of traffic or define an elastic network in front of AMQ 7 brokers. This article shows a sample AMQ Interconnect topology for scaling AMQ 7 brokers easily.
Continue reading “Scaling AMQ 7 Brokers with AMQ Interconnect”
Red Hat JBoss AMQ 7 provides fast, lightweight, and secure messaging for internet-scale applications. In addition, AMQ 7 components use industry-standard message protocols and support a wide range of programming languages and operating environments.
Therefore, AMQ 7 gives you the strong foundation you need to build modern distributed applications. Especially relevant is that multiple instances of AMQ 7 brokers can be grouped together to share message processing load.
Each broker manages its own messages and connections and is connected to other brokers with “cluster bridges” that are used to send topology information, such as queues and consumers, as well as load balancing messages.
AMQ 7 supports two different strategies for backing up a server: shared store and replication.
Continue reading “Automating AMQ 7 High Availability Deployment”
Messaging with JBoss A-MQ (broker), AMQP (protocol), and AMQP.Net Lite (Windows client) Made Easy
