Help Center/ Distributed Message Service for RocketMQ/ Service Overview/ Instance Versions
Updated on 2024-05-14 GMT+08:00
View PDF
Share

Instance Versions

This section compares Distributed Message Service (DMS) for RocketMQ versions and the instance types and architectures supported by each version.

Instance Types and Architectures

Table 1 Instance types and architectures

Version

Type

Architecture

4.8.0

Professional

Cluster

5.x

Basic

Single-node

Cluster

Professional (coming soon)

Single-node

Cluster

Any fault with a single-node instance may affect service SLA and make services unavailable. However, single-node instances are cost-effective so they are suitable for testing.

V5.x Advantages

Compared to v4.8.0, v5.x has the following advantages:

  • Advanced architecture

    V5.x comes with stateless proxies so proxy access is no longer a problem. V5.x provides POP consumption, which can reduce consumption accumulation.

  • Easy development

    SDKs in multiple languages that support gRPC protocol are available. APIs are simple and friendly.

  • Flexible cost

    Smaller flavors are available. Elastic scale-up helps reduce costs. Professional edition supports pay-per-use message storage, which is flexible compared to disk attachment where scale-down is not supported.

  • Better compatibility

    V5.x is compatible with RocketMQ v4.8.0 SDKs, allowing for seamless upgrade.

Comparing Single-node and Cluster Instances

Table 2 Differences between single-node and cluster instances

Dimension

Single-node

Cluster

Environment

Development, which has no requirement on performance and reliability

Production, which requires HA and no SPOF

Architecture

HA is supported by ECS, but cannot be ensured if ECS faults occur.

Distributed HA supports failover.

SLA

None

Reference SLA

Limitation
  • Specifications cannot be changed.
  • Versions cannot changed.
  • Specifications can be changed.
  • Versions cannot changed.