Release Notes for AMQ Interconnect 2.0
Release Notes for AMQ Interconnect 2.0 DEVELOPMENT PREVIEW
Making open source more inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
AMQ Interconnect 2.0 is a Development Preview release. Development Preview releases are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
Chapter 1. New and changed features
This release allows you connect services between OpenShift clusters, creating a service network. See the following guides for more details:
The Using the AMQ Interconnect router describes how to create router networks using AMQP. If router networks are your goal, Red Hat recommends using the AMQ Interconnect 1 LTS release.
1.1. Introduction to AMQ Interconnect 2.0
Interconnect 2.0 introduces a service network, linking services across the hybrid cloud. A service network enables communication between services running in different network locations. It allows geographically distributed services to connect as if they were all running in the same site.
For example, you can deploy your frontend in a public OpenShift cluster and deploy your backend in a private OpenShift cluster, then connect them into a service network.
A service network provides the following features:
- Security by default. All inter-site traffic is protected by mutual TLS using a private, dedicated certificate authority (CA).
- Easy connections between OpenShift clusters, even private clusters.
- A service network supports existing TCP-based applications without requiring modification.
- Monitor your application traffic spread across multiple OpenShift clusters using the service network console.
You deploy and manage a service network using the
1.2. TCP Protocol
This release of AMQ Interconnect supports TCP and any protocol overlayed on TCP to create a service network. Unlike the typical AMQ Interconnect use cases, this means that you can use existing applications without modification. While router networks are still supported, if AMQP is your only goal, Red Hat recommends using the AMQ Interconnect 1 LTS release.
Port negotiation limitation
If your protocol negotiates the communication port, for example active FTP, you cannot use that protocol to communicate across a service network.
Revised on 2021-04-08 11:54:38 UTC