Usage Limit


When using the Data Federation service, take note of the following usage limits:


Data Federation Resource Preparation

Before creating data federation channels, ensure that your OU has requested for the Data Federation resource through the EnOS Management Console > Resource Management page. The resource specification determines the performance of the data query through the data federation channels, and an allocated resource instance can be associated with only 1 channel. For more information about requesting for the Data Federation resource, see Data Federation Resource Specification.


Number of Channels

At most 10 channels (read, download, or write) can be created in an OU.


Number of Authorized Applications

At most 20 applications (service accounts) can be authorized to access data through a single channel.


Number of Data Sources

At most 10 data sources can be associated with a single channel.


Data Querying Interface Timeout

The timeout limit of the data querying interface is 5 minutes.


File Size Limit of the Data Writing Channel

When uploading files through the data writing channel, the size of each chunk must not exceed 10MB, and the total file size must not exceed 1GB.


Data Reading Capability of the Data Reading Channel

Theoretically, when the running resource configuration is 2CU, the amount of data (rows x columns) that can be read by the data reading channel should not exceed 700,000, and the converted JSON text should not exceed 15MB. When the running resource configuration is 3CU, the amount of data (rows x columns) that can be read by the data reading channel should not exceed 1,050,000, and the converted JSON text should not exceed 22.4MB. For the data reading capability with other running resource configuration, refer to data in the following table:


CU pod Resource for each pod Rows × Columns (x10000) Data Capability (MB)
2 1 2 70 15
3 1 3 105 22.5
4 1 4 140 30
5 2 2.5 87.5 18.75
6 2 3 105 22.5
7 2 3.5 122.5 26.25
8 2 4 140 30
9 2 4.5 157.5 33.75
10 2 5 175 38.5