Help Center/ Database Security Service/ User Guide/ Database Encryption/ Series 2/ Quick Start/ Quick Start Overview
Updated on 2026-09-24 GMT+08:00
View PDF
Share

Quick Start Overview

This chapter is designed for first-time platform users, helping them quickly understand the business system, grasp the difference between the Pre-Release mode and the standard mode, decide whether to use the Application-Plugin or Proxy mode during integration, and complete the configuration for the selected business scenarios.

  • Pre-Release Mode: The market offers a wide variety of database types, and the SQL syntax supported by these databases varies significantly. Database encryption products cannot parse all SQL statements across all database types; therefore, a Pre-Release feature has been introduced. In this mode, SQL statements that are not supported by the encryption system are executed within a test environment. The Pre-Release Mode does not encrypt or mask actual production data; instead, it simply logs any unparseable SQL statements into a file, providing a basis for evaluating whether these statements can be safely used in the production environment.
  • Standard Mode: In Standard Mode, the system provides encryption/decryption, data masking, and other functions based on the configured settings; it does not log SQL statements that cannot be parsed.

As explained in the Database Encryption Introduction section, database encryption products support both the Application-Plugin mode and the Proxy mode. Each of these modes differs from the standard mode; therefore, there are four distinct operating scenarios in total. The functionality of each mode is outlined in Table 1. We recommend using the Pre-Release mode first to assess the business systems to be integrated, in order to determine the impact of unsupported SQL queries on the business operations.

Table 1 Operating mode function comparison

Run Mode

Application-plugin Pattern

Proxy Pattern

Pre Release method

No encryption, decryption, or data masking functionality; only unresolvable SQL statements are logged.

No encryption, decryption, or data masking functionality; only unresolvable SQL statements are logged.

common mode

Features encryption, decryption, and data masking; does not log uninterpretable SQL statements.

Features encryption, decryption, and data masking; does not log uninterpretable SQL statements.

After determining the operating mode, before performing the integration operation, it is necessary to decide which integration approach to use—whether the Proxy pattern or the Application-Plugin pattern—since the characteristics of these two approaches are shown in Table 2.

Table 2 Comparison between the application-plugin pattern and the proxy pattern

Comparison Dimension

Application-plugin Pattern

Proxy Pattern

applicable scene

Applications developed using the Java programming language.

Applications developed using Java, C, C++, Python, or PHP.

Performance consumption

Low Performance Overhead.

High performance consumption.

compatibility

Low dependency on database version.

Highly dependent on a database version.

NOTE:

You need to query the database's compatible version.

Modification Cost

Low retrofitting cost (automated retrofitting).

Low retrofitting cost (automated retrofitting).

Implementation Cost

wide application.

It is widely used.

Whether integrating using the Proxy pattern or the Application-Plugin pattern, you must first create assets on the platform, generate keys, select the table fields to be encrypted, and encrypt the historical data. After completing these steps, proceed with configuring the specific features for either the Proxy pattern or the Application-Plugin pattern.

Parent Topic: Quick Start