public: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
public:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism to public:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism nick_didopublic:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 ====== Cloud Agnosticism ====== ====== Cloud Agnosticism ======
  
-[[private:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]+[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
  
 ===== Discussion ===== ===== Discussion =====
  
-Cloud Agnosticism is an architectural characteristic that limits dependence on the proprietary interfaces, services, data formats, software development kits, or operational mechanisms of a particular [[private:99_annexes:annex-b-terms-and-definitions:c:cloud_provider|Cloud Provider]].+Cloud Agnosticism is an architectural characteristic that limits dependence on the proprietary interfaces, services, data formats, software development kits, or operational mechanisms of a particular [[public:99_annexes:annex-b-terms-and-definitions:c:cloud_provider|Cloud Provider]].
  
 A cloud-agnostic architecture expresses common capabilities through provider-independent concepts, contracts, and interfaces. Provider-specific implementations translate those common capabilities into the mechanisms required by each Cloud Provider. A cloud-agnostic architecture expresses common capabilities through provider-independent concepts, contracts, and interfaces. Provider-specific implementations translate those common capabilities into the mechanisms required by each Cloud Provider.
Line 11: Line 11:
 Cloud Agnosticism does not require every Cloud Provider to offer identical capabilities. The architecture may identify optional capabilities, provider-specific constraints, or controlled extensions without allowing provider-specific logic to spread throughout the core system. Cloud Agnosticism does not require every Cloud Provider to offer identical capabilities. The architecture may identify optional capabilities, provider-specific constraints, or controlled extensions without allowing provider-specific logic to spread throughout the core system.
  
-[[private:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism|Cloud Agnosticism]] can support [[private:99_annexes:annex-b-terms-and-definitions:p:portability|Portability]] by reducing dependence on a particular Cloud Provider. Cloud Agnosticism does not, by itself, establish Portability, because movement to another platform, runtime, deployment environment, or operational context may require adaptation, verification, requalification, or additional evidence.+[[public:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism|Cloud Agnosticism]] can support [[public:99_annexes:annex-b-terms-and-definitions:p:portability|Portability]] by reducing dependence on a particular Cloud Provider. Cloud Agnosticism does not, by itself, establish Portability, because movement to another platform, runtime, deployment environment, or operational context may require adaptation, verification, requalification, or additional evidence.
  
 ===== Definition ===== ===== Definition =====
  
-//architectural characteristic that limits dependence on the proprietary interfaces, services, data formats, software development kits, or operational mechanisms of a particular [[private:99_annexes:annex-b-terms-and-definitions:c:cloud_provider|cloud provider]]//+//architectural characteristic that limits dependence on the proprietary interfaces, services, data formats, software development kits, or operational mechanisms of a particular [[public:99_annexes:annex-b-terms-and-definitions:c:cloud_provider|cloud provider]]//
  
 ===== Source ===== ===== Source =====
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. [[private:99_annexes:annex-b-terms-and-definitions:p:portability|Portability]] concerns the ability to transfer or adapt a system, artifact, or workload between environments.+Cloud Agnosticism concerns architectural dependence. [[public: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 =====
  • public/99_annexes/annex-b-terms-and-definitions/c/cloud_agnosticism.1789260136.txt.gz
  • Last modified: 2026/09/12 17:42
  • by nick_dido