DataWorks feature Practice series to help you analyze the pain points in the process of business implementation and improve the efficiency of business function use!
Past review:
- DataWorks Features Practice Overview 01 — Data Synchronization Solutions: Introduces the data synchronization solutions available in different scenarios.
- DataWorks Practice Overview 02 — Exclusive Data Integration Resource Group: introduces the solutions and precautions for connecting resource groups to the network during data synchronization.
In the previous two installtions, you learned about the main points of data synchronization using DataWorks: data synchronization solutions and resource groups. In practical applications, we often need to separate the development environment from the production environment. The development environment is used for data synchronization testing, and the production environment is used for production data synchronization processing. This installment introduces you to the key points that DataWorks uses to separate development from production.
Recommended function: Standard mode — The development environment and production environment are isolated
To facilitate user production data with different security control requirements, DataWorks provides you with two workspace modes, simple mode and standard mode. Simple mode cannot set the development environment and production environment, while standard mode provides both development environment and production environment, and isolates the two environments. You can perform data tasks in both development and production environments.
Part1: Simple mode and standard mode DataWorks workspace
First, I’ll show you the main differences between the two modes of workspace.
As can be seen from the above, the standard mode workspace of DataWorks can isolate the development and production environments. Therefore, if you use the standard mode, the precautions for using the development and production environments are inconsistent during data access and permission control.
Part2: Data access of workspaces in different modes
You can set the data access mode of the workspace for different modes in the Workspace Configuration > Computing Engine Information area of DataWorks.
Part3: Permission management features of workspaces in different modes
DataWorks adopts THE RBAC permission model for users to manage the permission of all page visible functions and APIS of DataWorks, and this permission system has a natural mapping relationship with the RBAC role system of MaxCompute. For details, see Member and Role Management and Member Role and Permission Relationship. Different types of workspaces have different permission management features and advantages and disadvantages. The following table compares and introduces the permission segmentation features of the two types of workspaces.
Table naming specifications for MaxCompute engines in different schemas
In simple mode, there is no distinction between development environment and production environment, and the development library is the production library. In standard mode, the development environment and production environment can be isolated. The names of database tables in the development environment and production environment are different. If you need to access database tables in the production environment from the development environment, strictly distinguish database table names based on the following naming conventions to avoid misoperations in the production environment.
More information about the differences between the simple and standard modes can be found in the help center.
Scene practice:
Permission management and standardized data development: Through this practice, you can understand the standard process and permission management suggestions for user data development in a standard-mode workspace.
The original link
This article is the original content of Aliyun and shall not be reproduced without permission.