Property Manager to Delivery Manager mapping

Transitioning to a modular architecture doesn't mean forgetting your Akamai expertise. See how familiar Property Manager configurations translate into Delivery Manager's new, Git-like concepts.

Delivery Manager component	Description	Property Manager equivalent
Workspace	A the top-level logical container in the CDN architecture that organizes all resources for a single application or service.	No direct equivalent. Partially replaces the concept of a flat property group, but enforces strict security boundaries and access control.
Environment	An isolated configuration variant of an application or service at a specific stage of its lifecycle (such as development, testing, or production). Each environment maintains its own independent deployment and version history. Analogous to a Git branch.	Property. A basic configuration container, but lacks native isolation and requires manual lifecycle management.
Service hostname set	A collection of customer domains managed independently from rules. Adding a domain, renewing a TLS certificate, or modifying routes doesn't impact your environment versions.	Hostname bucket, designed to decouple domains from configuration logic, or the standard property hostnames bound to a specific property version, forcing a full rule-tree activation for basic certificate updates or routing changes.
Default rule set	The primary rule tree for an environment, containing product default settings. Applies globally to all traffic unless explicitly overridden downstream.	Default rule and its built-in product child rules located at the root of the monolithic rule tree.
Custom rule set	A self-contained block of logic (caching, redirects) that can be managed by different teams within the boundary of a single environment.	Microservice include that provides modularity and delegation options, or logical sections of a monolithic rule tree.
Shared rule set	Shared logic made available to all workspaces and environment configurations in a contract. Shared rule sets can be helpful for creating common, iterable policies or organizational standards across environments. Updates can be inherited automatically or explicitly pinned to independent versions.	Common settings include that provides the ability to share standardized rules across multiple parent configurations.
Origin	A defined source for content, which can be created once and shared across multiple workspaces.	Origin behavior, which forces users to redefine backend configurations inline across separate properties, adding duplicate overhead.
Route	Flexible mapping of service hostname sets to specific environments using different routing modes.	Implicit hostname mapping within a property version.
Variable	Placeholders for settings (like TTLs) that can be shared across environments or overridden locally to enable reuse of rule sets. Covers two types: compile-time variables that resolve when you activate your configuration, and run-time variables computed during HTTP request processing.	PM variable, but without workspace-wide sharing mechanisms, forcing users to hardcode stage-specific contexts or manage variables per property.