Overview and Network Environment Preparation

Overview

ROMA MQS is fully compatible with the Kafka protocol and can be directly connected to the open-source Kafka client. If the SASL authentication mode is used, use a certificate file provided by the cloud service on the basis of the open-source Kafka client.

This guide describes how to collect MQS connection information, such as the MQS connection address and port, certificate used by the SASL connection, and public network access information. It also provides connection examples in Java and Python languages.

The examples in this guide present only API calls of Kafka. For details about production and consumption APIs, see the Kafka official website.

Network Environment of the Client

The client can access MQS in any of the following ways:

• Subnet address in a VPC

  If the client is an ECS on the cloud and located in the same VPC in a region as MQS, the client can directly access the subnet address in the VPC provided by MQS.

• VPC peer-to-peer connection

  If the client is an ECS on the cloud and located in a different VPC but the same region as MQS, the client can access the subnet address in the VPC provided by MQS after establishing a VPC peer-to-peer connection.

• Public network

  If the client is located in another network environment or is in a different region from MQS, the client accesses the public network address of MQS.

  For public access of the instance, you need to modify the security group bound to the ROMA Connect instance and add inbound rules to allow access from the external network through ports 9094, 9095, and 9096.

In different network environments, client configurations are the same except the connection address. Therefore, this guide describes how to set up the client development environment by using the subnet address in the same VPC as an example.

If the connection times out or fails, check whether the network connection is normal. You can use Telnet to check the IP address and port number of the instance.