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 API Update Policy
More DMS APIs will be open with the development of existing services and rollout of new services.
Based on service requirements, new functions will be provided and more APIs with more capabilities will be open to tenants.
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.
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.