SDK overview

Introduction

A Software Development Kit (SDK) is a set of tools for developing applications. It includes resources such as samples, libraries, toolchains, and build scripts. You can use an SDK to develop and compile applications directly in its environment without additional configuration.

SDKs

Usage notes

Instance endpoints

Your client application connects to Message Queue for Apache Kafka using various endpoints to send and receive messages.

• Default Endpoint: Allows clients to connect to a Message Queue for Apache Kafka instance to send and receive messages.
• SSL Endpoint: Connect to a Message Queue for Apache Kafka instance by using an SSL endpoint and use the PLAIN mechanism to send and receive messages. The PLAIN mechanism is a simple username and password authentication method. Message Queue for Apache Kafka optimizes the PLAIN mechanism, which lets you dynamically add SASL users without restarting the instance.
  Important If your instance uses a 1024-bit SSL certificate and you require stronger security, you can upgrade it to a 4096-bit certificate. For more information, see Upgrade the SSL certificate algorithm.
• SASL Endpoint: In a VPC, you can connect to Message Queue for Apache Kafka using a SASL endpoint and use the PLAIN or SCRAM mechanism to send and receive messages. SASL supports the following authentication mechanisms:
  • PLAIN: A simple username and password authentication method. The PLAIN mechanism in Message Queue for Apache Kafka allows you to dynamically add SASL users without restarting the instance.
  • Message Queue for Apache KafkaSCRAM-SHA-256: A secure authentication mechanism that uses a hash algorithm on both the client and server to verify usernames and passwords. This mechanism provides higher security than the PLAIN mechanism. It also lets you dynamically add SASL users without an instance restart.

For more information about endpoints, see Endpoint comparison.

Demo usage

Select the demo that matches your instance. Configure the demo file and run it to send and receive messages. For detailed instructions, see the documentation for the specific language.

References

• Deploy a Message Queue for Apache KafkaMessage Queue for Apache Kafka instance based on your required network type. For more information, see Connect to a Message Queue for Apache Kafka instance over a VPC and Deploy an instance accessible from the internet and a VPC.
• Create the required consumer group and topic. For more information, see Step 3: Create resources.
• The default SASL user for an internet or VPC instance provides only identity verification. It has read and write permissions for all topics and consumer groups. If you require more granular access control, you can enable the ACL feature. You can then create SASL users and grant them specific permissions to send and receive messages in Message Queue for Apache Kafka. Enabling the ACL feature revokes the permissions of the default SASL user. For more information, see Grant permissions to SASL users.