Product Specifications
ROMA Connect Instance Specifications
The following table lists the ROMA Connect instance specifications in each edition.
|
Instance Edition |
Number of Systems Supported |
Number of Connections Supported |
Applicability |
|---|---|---|---|
|
Basic edition |
5 to 10 |
25 |
Small-sized enterprises |
|
Professional |
10 to 20 |
80 |
Small- and medium-sized enterprises |
|
Enterprise |
20 to 30 |
200 |
Medium- and large-sized enterprises |
|
Platinum |
More than 30 |
800 |
Large-sized enterprises |
The numbers of connections and systems listed are for reference only. For details about the number of resources (such as data integration tasks, 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. You can set up multiple connections between a service system and a ROMA Connect instance.
- Number of connections: A connection refers to an interaction between a service system and ROMA Connect. The number of connections varies depending on the functional module in ROMA Connect that you want to connect. The following table describes the mappings between the number of resources and the number of connections.
Table 2 Mappings between the number of resources and the number of connections Functional Module
Mapping
FDI
Two FDI tasks in the running state occupy one connection.
APIC
- 10 hosting APIs (that do not use custom backends as backend services) occupy one connection.
- Five function backends or data backends occupy one connection.
MQS
Three topics occupy one connection.
LINK
1000 devices occupy one connection.
FDI Specifications
The following table lists the FDI specifications supported by a ROMA Connect instance.
|
Instance Edition |
Relational Database Collection Throughput (Mbit/s) |
Message System Collection Throughput (Mbit/s) |
Unstructured Storage Collection Throughput (Mbit/s) |
|---|---|---|---|
|
Basic |
0.5 |
4 |
2 |
|
Professional |
1 |
5 |
3 |
|
Enterprise |
1.5 |
7 |
4.5 |
|
Platinum |
2 |
10 |
6 |
APIC Specifications
The following table lists the APIC specifications supported by a ROMA Connect instance.
The APIC specifications are obtained by testing in the following conditions:
- Connection protocol: HTTPS
- Connection type: long connection
- Concurrency: 100
- Authentication mode: app authentication
- Size of the returned data: 1 KB
- Bandwidth: 10 Mbit/s
|
Instance Edition |
API Forwarding (TPS) |
Data API (TPS) |
|---|---|---|
|
Basic |
4000 |
400 |
|
Professional |
6000 |
600 |
|
Enterprise |
8000 |
800 |
|
Platinum |
10,000 |
1000 |
MQS Specifications
Open-source compatibility: ROMA Connect is fully compatible with open-source Kafka 1.1.0 and 2.3.0, and is compatible with open-source Kafka APIs. It has all message processing features of native Kafka. ROMA Connect supports clients later than version 0.10. Use a client version that is consistent with the service version.
The following table lists the MQS specifications supported by a ROMA Connect instance. When selecting the specifications, you are advised to reserve 30% of the bandwidth to ensure stable running of your applications.
|
Instance Edition |
Bandwidth |
TPS (High-Throughput) |
TPS (Synchronous Replication) |
Maximum Number of Partitions |
Specifications |
|---|---|---|---|---|---|
|
Basic |
100 MB/s |
100,000 |
60,000 |
300 |
Recommended for up to 3000 client connections, 60 consumer groups, and 70 MB/s service traffic. |
|
Professional |
300 MB/s |
300,000 |
150,000 |
900 |
Recommended for up to 10,000 client connections, 300 consumer groups, and 210 MB/s service traffic. |
|
Enterprise |
600 MB/s |
600,000 |
300,000 |
1800 |
Recommended for up to 20,000 client connections, 600 consumer groups, and 420 MB/s service traffic. |
|
Platinum |
1200 MB/s |
1.2 million |
400,000 |
1800 |
Recommended for up to 20,000 client connections, 600 consumer groups, and 840 MB/s service traffic. |
LINK Specifications
ROMA Connect supports device access using MQTT 3.1 and MQTT 3.1.1. The following table lists the LINK specifications supported by an instance.
|
Instance Edition |
Upstream Message |
Downstream Message |
|---|---|---|
|
Basic |
10,000 TPS for 20,000 online devices |
1,000 TPS for 20,000 online devices |
|
Professional |
20,000 TPS for 40,000 online devices |
1,500 TPS for 40,000 online devices |
|
Enterprise |
40,000 TPS for 100,000 online devices |
2,000 TPS for 100,000 online devices |
|
Platinum |
100,000 TPS for 500,000 online devices |
5,000 TPS for 500,000 online devices |
Last Article: Application & Data Integration of Corporation Groups
Next Article: Quotas
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.