Cloud Portability [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.
====== Cloud Portability ======

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

===== Discussion =====

Cloud Portability is the ability to transfer or re-realize applications, data, configurations, workloads, or infrastructure intent between cloud environments while preserving defined characteristics.

The transferred or re-realized subject may include:

  * An application
  * A workload
  * Data
  * An [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]]
  * An [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_blueprint|Infrastructure Blueprint]]
  * A [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]]
  * A Platform Deployment
  * A service composition

The characteristics preserved during transfer or re-realization may include:

  * Functional behavior
  * Information meaning
  * Information structure
  * Security characteristics
  * Performance characteristics
  * Availability characteristics
  * Operational behavior
  * Applicable constraints
  * Applicable [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]]

Cloud Portability may require:

  * Separation of [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_information|Platform Independent Information]] from [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_information|Platform Specific Information]]
  * Mapping to a target [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_implementation|Provider Implementation]]
  * Replacement of provider-specific services
  * Transformation of configuration formats
  * Conversion of data formats
  * Substitution of resource types
  * Application of target-platform parameters
  * Validation against target-environment Acceptance Criteria

Cloud Portability differs from interoperability:

  * Cloud Portability concerns transfer or re-realization between cloud environments
  * Interoperability concerns interaction between systems or components

Cloud Portability also differs from migration:

  * Migration is the activity that moves or transforms a subject
  * Cloud Portability is the capability that allows the subject to be moved or re-realized while preserving defined characteristics

===== Definition =====

//portability that enables an application, workload, data set, configuration, or infrastructure specification to be transferred or re-realized between cloud environments while preserving defined characteristics//

===== Source =====

Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

===== Note =====

Cloud Portability does not require identical implementations across cloud environments.

A portable realization may use different:

  * Resource types
  * Service names
  * Interfaces
  * Machine images
  * Network constructs
  * Storage technologies
  * Security mechanisms
  * Deployment tools

The applicable requirements determine which characteristics must remain equivalent after transfer or re-realization.

Cloud Portability may be limited by:

  * Provider-specific services
  * Proprietary interfaces
  * Data-transfer constraints
  * Licensing restrictions
  * Security constraints
  * Regulatory constraints
  * Performance differences
  * Operational dependencies

Cloud Portability does not by itself establish that migration is automated, cost-free, lossless, or possible without modification.

===== Example =====

A platform-independent Infrastructure Blueprint is realized on two cloud providers by mapping its compute, storage, networking, identity, and monitoring requirements to each provider's services. Each resulting Infrastructure Environment satisfies the same defined Acceptance Criteria even though the Platform Specific Information differs.

----

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