Edge Deployment [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Edge Deployment ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]

===== Discussion =====

An Edge Deployment is an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] that deploys one or more identified deployment subjects to an [[dido:99_annexes:annex-b-terms-and-definitions:e:edge_environment|Edge Environment]].

Deployment subjects may include:

  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_resource|Infrastructure Resources]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|Virtual Machines]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes_cluster|Kubernetes Clusters]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:containerized_workload|Containerized Workloads]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service|Platform Services]]
  * Configuration
  * Security controls
  * Monitoring capabilities
  * Operational data

An Edge Deployment may need to account for:

  * Limited network bandwidth
  * Intermittent connectivity
  * Restricted external connectivity
  * Limited computing capacity
  * Limited storage capacity
  * Local security controls
  * Physical access constraints
  * Local operational authority
  * Dependency availability
  * Local update and rollback procedures

An Edge Deployment differs from a cloud deployment:

  * An Edge Deployment targets an Edge Environment
  * A cloud deployment targets an Infrastructure Environment supplied through cloud capabilities

An Edge Deployment may also form part of a Hybrid-Cloud Deployment when related deployment subjects operate across cloud and Edge Environments.

An Edge Deployment does not necessarily imply disconnected or air-gapped operation.

===== Definition =====

//[[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|infrastructure deployment]] that deploys one or more identified deployment subjects to an [[dido:99_annexes:annex-b-terms-and-definitions:e:edge_environment|Edge Environment]]//

===== Source =====

Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

===== Note =====

The applicable deployment specification should identify:

  * The target Edge Environment
  * The deployment subjects
  * The applicable environment constraints
  * Required dependencies
  * Required configuration
  * Applicable [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]]
  * Required deployment validation
  * Required rollback behavior

The term does not prescribe a device class, edge platform, orchestration technology, provider, network architecture, or connectivity model.

===== Example =====

Crucible performs an Edge Deployment by deploying a Containerized Workload, its configuration, and required Platform Services to an Edge Environment located within a remote industrial facility.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>