Understanding DXP Cloud Environments¶
A DXP Cloud project can have multiple environments, each for a different purpose (e.g., development, staging, production, etc.). Each environment has a unique name that is the project ID plus the environment ID. For example, the staging and production environments for a project named acme can be named acme-uat and acme-prd, respectively.
Once an environment name and location have been chosen, it’s not possible to rename or change to a different location automatically. If you need to perform such actions, please contact support.
Despite this naming connection, each environment is independent. They’re segregated by a private network that allows services from the same environment to communicate in a secure manner without having to access the public internet.
You can access these environments from the selector menu at the upper left.
Different environments can be located in different regions. For example, a company with its engineering team in Europe but most clients in North America can have its development environment in Frankfurt and its production environment in Oregon. Having a location close to its users’ requests improves network latency.
Here’s a list of the DXP Cloud regions currently available.
The environment type is a classification that distinguishes an environment configuration. There are two environment types:
Besides having different prices and computing power, these environment types differ in how their backup and database services function.
Backup: Data backups are automatically created on a regular schedule by default.
Database: Data is replicated in multiple availability zones and contains enhanced IOPS.
Backup: Data backups are not created automatically by default.
Database: Data is present in a single availability zone and contains regular IOPS.