| Next revision | Previous revision |
| dido:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism [2026/07/13 11:15] – created nick_dido | dido:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| 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. |
| |
| Within the Crucible architecture, the [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_abstraction|Provider Abstraction]], [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_contract|Provider Contract]], [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_plugin|Provider Plugin]], and [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_registry|Provider Registry]] support Cloud Agnosticism. | [[dido:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism|Cloud Agnosticism]] can support [[dido: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 ===== |
| 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 ===== |