• API White Paper

wp
  1. Help Center
  2. API White Paper
  3. API Reference
  4. Open Telekom Cloud API Overview
  5. Open Telekom Cloud DMS API Overview

Open Telekom Cloud DMS API Overview

Distributed Message Service (DMS) is a message middleware service using highly available distributed cluster technologies and features large scale, high availability, highly concurrent access, scalability, and full hosting. DMS enables cloud applications to decouple from each other, making it a cost-effective solution.

Tenants can use message queue management APIs to create and delete message queues.

Tenants can use the message production and consumption APIs to produce and consume messages.

DMS API Open Scope and Principles

DMS API Description

  • DMS provides the following APIs for queue management:
    • API for creating queues: Tenants use this API to create queues through which messages are produced.
    • API for creating consumption groups: Tenants can use this API to create consumption groups for consuming messages.
    • API for querying queues: Tenants can use this API to query created queues.
    • API for querying information about a specified queue: Tenants can use this API to query information about a specified queue.
    • API for querying consumption groups: Tenants can use this API to query consumption groups contained in a specified queue.
    • API for deleting queues: Tenants can use this API to delete unused queues.
    • API for deleting consumption groups: Tenants can use this API to delete consumption queues.
    • API for querying quotas: Tenants can use this API to query how many queues can be created.
  • DMS provides the following APIs for message production and consumption:
    • API for producing messages: Tenants can use this API to produce messages in a specified queue.
    • API for consuming messages: Tenants can use this API to consume messages in a specified queue.
    • API for consumption confirmation: Tenants can use this API to confirm consumed messages.

DMS API Update Policy

More DMS APIs will be open with the development of existing services and rollout of new services.

DMS API Update Method

Based on service requirements, new functions will be provided and more APIs with more capabilities will be open to tenants.

Backward Compatibility of DMS APIs

New APIs are added based on service requirements and kept compatible with existing APIs. Interim solutions will be formulated for APIs to be deleted and will be sent to users.

API updating complies with the backward compatibility rule.

API change history is released with the version release, allowing users to clearly know the API updates.

Migration Plan for DMS API Updating

DMS development takes the migration plan into account when new API versions are being designed.

APIs of the new version must be compatible with those of earlier versions semantically. APIs that are no longer supported must be marked (such as with @deprecated) two versions in advance. During this period, the APIs must still be available and an alternative must be provided.