dido:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
dido:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism [2026/07/13 11:18] – nick_didodido:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 25: Line 25:
 Cloud Agnosticism does not mean that every deployment can move between Cloud Providers without adaptation. Provider capabilities, service availability, identity models, networking, data services, and regulatory constraints may affect portability. Cloud Agnosticism does not mean that every deployment can move between Cloud Providers without adaptation. Provider capabilities, service availability, identity models, networking, data services, and regulatory constraints may affect portability.
  
-Cloud Agnosticism concerns architectural dependence. [[dido:99_annexes:annex-b-terms-and-definitions:p:portability|Portability]] concerns the ability to transfer or adapt a system, artefact, or workload between environments.+Cloud Agnosticism concerns architectural dependence. [[dido:99_annexes:annex-b-terms-and-definitions:p:portability|Portability]] concerns the ability to transfer or adapt a system, artifact, or workload between environments.
  
 ===== Example ===== ===== Example =====
  • dido/99_annexes/annex-b-terms-and-definitions/c/cloud_agnosticism.1783966739.txt.gz
  • Last modified: 2026/07/13 11:18
  • by nick_dido