DataWorks provides workspaces in basic mode and standard mode for you to develop data under different security control requirements. This topic describes these two modes, including their advantages, risks, and accounts that are allowed to perform operations in each mode.

Basic mode

In basic mode, you can bind only one compute engine of each type to a DataWorks workspace, which can be a MaxCompute project, an E-MapReduce instance, or a Hologres database. A workspace in basic mode does not isolate the development environment from the production environment. In this workspace, you can only perform basic data development but cannot completely control the data development process and table permissions.

A workspace in basic mode has the following benefits and risks:
  • Advantages: This mode is easy to use. The scheduling system can periodically run a node to produce data immediately after you commit the node, without the need to deploy the node.
  • Risks: Developers can add and modify code without the need for authorization, and the added or modified code immediately takes effect in the scheduling system. This makes the production environment unstable. In addition, if this workspace is bound to a MaxCompute compute engine, developers have the read and write permissions on all tables of the MaxCompute project by default. Developers can add, delete, and modify any table in the workspace. This puts data at risk.

Standard mode

In standard mode, you can bind two compute engines of each type to a DataWorks workspace, which can be MaxCompute projects, E-MapReduce instances, or Hologres databases. The standard mode differs from the basic mode in the following aspects:
  • You can modify nodes only in the development environment, but cannot modify them in the production environment.
  • After you commit a node, the scheduling system runs the node in the development environment as a smoke test. To automatically trigger running of this node, you must deploy it to the production environment.

    You can deploy a node only after you obtain approval from a workspace administrator or administration expert.

Access accounts for workspaces in basic mode and standard mode

You can specify the accounts that are allowed to perform operations in workspaces in basic mode and standard mode in the Computing Engine information section of the Workspace Management page. For more information, see Configure a workspace.
Workspace mode Compute engine type Environment Access account
Standard mode MaxCompute Development environment Only the current logon account can perform operations.
Production environment The following accounts can be specified to perform operations:
  • Alibaba Cloud account
  • Resource Access Management (RAM) user
E-MapReduce Development environment Only the accounts with the AccessKey IDs and AccessKey secrets specified in the New EMR cluster dialog box can perform operations.
Production environment
Hologres Development environment Only the current logon account can perform operations.
Production environment The following accounts can be specified to perform operations:
  • Alibaba Cloud account
  • RAM user
Basic mode MaxCompute Development environment, which is also the production environment Only the current logon account can perform operations.
The following accounts can be specified to perform operations:
  • Node owner
  • Alibaba Cloud account
E-MapReduce Development environment, which is also the production environment Only the accounts with the AccessKey IDs and AccessKey secrets specified in the New EMR cluster dialog box can perform operations.
Hologres Development environment, which is also the production environment Only the current logon account can perform operations.
The following accounts can be specified to perform operations:
  • Alibaba Cloud account
  • RAM user