DataWorks provides workspaces in basic mode and standard mode for you to develop data under different security control requirements. This topic describes the differences between and access accounts for workspaces in basic mode and standard mode.
Workspaces in basic mode
In basic mode, a DataWorks workspace can be bound to only one compute engine of each type, which can be a project, an instance, or a database. A workspace in basic mode does not isolate the development environment from the production environment. In this workspace, you can perform only basic data development but cannot completely control the data development process and table permissions.
- Benefits: 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, modify, and commit code to the scheduling system without the need for approval. 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 create, delete, and modify a table in the workspace. This puts data at risk.
Workspaces in standard mode
- You can modify code only in the development environment, but cannot modify code in the production environment.
- After you commit a node, the scheduling system runs the node in the development environment
as a smoke test. The node is not automatically scheduled. If you want this node to
be automatically scheduled, you must deploy it to the production environment.
You can deploy a node only after you obtain approval from a workspace administrator or an administration expert.
Access accounts for workspaces in basic mode and standard mode
| Workspace mode | Compute engine type | Environment | Access account |
|---|---|---|---|
| Standard mode | MaxCompute | Development environment | Only the current logon node owner can perform operations. |
| Production environment | The following accounts can be specified to perform operations:
|
||
| 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 node owner can perform operations. | |
| Production environment | The following accounts can be specified to perform operations:
|
||
| Basic mode | MaxCompute | Development environment, which is also the production environment | Only the current logon node owner can perform operations.
The following accounts can be specified to perform operations:
|
| 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 node owner can perform operations.
The following accounts can be specified to perform operations:
|