The DLC Gateway is a Serverless unified access gateway service deeply optimized based on Apache Kyuubi. Through the gateway, you can achieve stable and secure access to DLC data and standard computing engines using standard APIs like Hive JDBC, Presto JDBC, DLC JDBC, and Tencent Cloud API. This reduces the complexity of managing large-scale access to computing engines. For example, you can submit SQL tasks and ETL jobs to the designated standard computing engine via the gateway.
Gateway Value
The gateway is a unique service of the DLC Standard Engine, offering users benefits such as reduced query latency, enhanced security and high availability, and flexible access:
Reduced query latency: The DLC Gateway can significantly reduce query processing time, especially enhancing the performance of interactive analysis on small data sets.
More access method support: The gateway supports Hive JDBC/Presto JDBC connections to the DLC Standard Engine, accommodating various query scenes.
Enterprise-Level security: Ensures high-level security through identity verification with CAM authentication parameters (AK/SK) and controls access permissions for sub-users on the engine.
High availability: The gateway offers enhanced availability and load balancing, supporting scaling to handle extremely high concurrent queries.
Upgrade Specifications
DLC provides a default specification of 2 CU for users. If your business scene requires more resources, you will need to purchase an upgrade.
1. Only one gateway can be created within a engine network.
2. The gateway can simultaneously manage multiple Standard Spark Engines and Presto Engines.
Note:
The gateway only supports specific specifications (2 CU, 16 CU, 32 CU, 64 CU). Different specifications are suited to managing clusters of varying sizes. For more details, see Suggestions for instance specification. Specification Recommendations
The DLC Gateway provides high availability and load balancing to support higher query concurrency and effectively reduce the average query time for small data sets by shortening the query path. It is recommended to select the gateway specification based on the number of engines you plan to manage and the maximum query concurrency (QPS) of your business scene. The specific recommendations are detailed in the table below. For example, if Client A plans to deploy 20 DLC Standard Engines in the Shanghai region, with a historical maximum concurrency of 300 QPS, the 32 CU specification would be a suitable choice.
|
2 CU | 30/50 | 100 | 4 | 50 | No |
16 CU | 80/150 | 250 | 12 | 150 | Yes |
32 CU | 220/400 | 600 | 35 | 400 | Yes |
64 CU | 400/600 | 1000 | 70 | 700 | Yes |
If you have any questions about selecting the appropriate gateway specification, you can Submit a ticket to contact us.
Was this page helpful?