Help Center/ ROMA Connect/ Service Overview/ Edition Differences (New Version)
Updated on 2024-06-06 GMT+08:00
View PDF
Share

Edition Differences (New Version)

Recommended Edition Specifications

The following table lists the recommended specifications for the new version.

Table 1 Recommended specifications

Number of Systems Supported

Estimated Number of RCUs

Applicability

Less than 5

5

Small enterprises

5 to 10

20

Small enterprises

10 to 20

40

Small- and medium-sized enterprises

20 to 30

80

Medium- and large-sized enterprises

More than 30

150

Large enterprises

The numbers of RCUs and systems listed are for reference only. For details about the number of resources (such as application flows, APIs, and message topics) that can be created, see Quota Limits. To ensure the performance of ROMA Connect, create and use resources within the specified specifications.

  • Number of systems: A system refers to a user's service system, and the number of systems refers to the number of service systems interconnecting with a ROMA Connect instance. Multiple connections can be established between a service system and a ROMA Connect instance.
  • Number of RCUs: The ROMA Compute Unit (RCU) is the capability compute unit of the new version. Each RCU can be allocated to different integration capabilities, including FDI, APIC, MQS, LINK, and composable applications. The performance specifications of each integration capability depend on the number of RCUs allocated. More RCUs indicate higher specifications.

Note that minimum RCUs and adjustments vary with the integration capability.

Specifications

The specifications of each integration capability of the new version vary with the number of allocated RCUs. Table 2 lists the specifications of each RCU.

  • The following performance data comes from lab tests and may differ from that in actual service scenarios.
  • Once FDI is enabled, the number of FDI tasks for both message and non-message data is fixed to 1000 and does not change with RCUs.
Table 2 Specifications

Integration Capability

Indicator

Specifications/RCU

Minimum RCUs

Minimum Adjustment

Composite Application (Flow Running)

Number of running flows

30

2

1

APIC (API Management)

API forwarding

1000 TPS

2

1

Number of hosted APIs

100

APIC (Data/Function API)

Data/Function API forwarding

100 TPS

2

1

Number of custom backends

50

API traffic

0.24 Mbit/s

FDI

Non-message data traffic

About 2 Mbit/s, up to 4 Mbit/s per task

4

2

Message data traffic

About 5 Mbit/s, up to 10 Mbit/s per task

MQS

Message traffic

30 Mbit/s

3

1 (Increasing only)

Disk

500 GB

Number of partitions

250

LINK

Number of online devices

10,000

2

1

Number of concurrent device messages

2500 TPS

The MQS specifications are obtained by testing in the following conditions:

  • Connection: intranet
  • Authentication: SASL_SSL
  • Data size: 1 KB/10 KB
  • Disk type: ultra-high I/O, SSD

The LINK specifications are obtained by testing in the following conditions:

  • Upstream message
    • Connection: intranet
    • Message size: 512 bytes
    • Message destination: MQS topic
The FDI specifications are obtained by testing in the following conditions:
  • Three concurrent tasks in each of the following scenarios:
    • MySQL to MySQL
    • OBS to OBS
    • Kafka to Kafka
  • Data read and write: 1 million records
  • Data migration volume: 1 GB

The APIC specifications are obtained by testing in the following conditions:

  • Backend type: shubao
    • Connection: persistent/short connection
    • Connection protocol: HTTP/HTTPS
    • Concurrency: at least 4000
    • Authentication: none
    • Size of the returned data: 1 KB
    • Bandwidth: 10 MB/s
    • Average backend response latency: 10 ms
  • Backend Type: LiveData
    • Connection: persistent/short connection
    • Connection protocol: HTTP/HTTPS
    • Concurrency: at least 400
    • Authentication: none
    • Size of the returned data: 1 KB
    • Bandwidth: 10 MB/s
    • Average backend response latency: 10 ms