public:99_annexes:annex-b-terms-and-definitions:p:provider_abstraction

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:p:provider_abstraction [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:p:provider_abstraction to public:99_annexes:annex-b-terms-and-definitions:p:provider_abstraction nick_didopublic:99_annexes:annex-b-terms-and-definitions:p:provider_abstraction [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 ====== Provider Abstraction ====== ====== Provider Abstraction ======
  
-[[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 =====
  
-A Provider Abstraction defines a provider-independent representation of the capabilities, operations, inputs, outputs, errors, and lifecycle behaviors required from one or more [[private:99_annexes:annex-b-terms-and-definitions:p:provider|Providers]].+A Provider Abstraction defines a provider-independent representation of the capabilities, operations, inputs, outputs, errors, and lifecycle behaviors required from one or more [[public:99_annexes:annex-b-terms-and-definitions:p:provider|Providers]].
  
 The abstraction separates the requesting software from provider-specific interfaces, software development kits, data formats, authentication mechanisms, and operational details. The abstraction separates the requesting software from provider-specific interfaces, software development kits, data formats, authentication mechanisms, and operational details.
Line 11: Line 11:
 A Provider Abstraction allows core functions to request capabilities through a stable architectural boundary while specialized implementations translate those requests into provider-specific operations. A Provider Abstraction allows core functions to request capabilities through a stable architectural boundary while specialized implementations translate those requests into provider-specific operations.
  
-Within the Crucible architecture, the Provider Abstraction supports cloud agnosticism by preventing provider-specific logic from spreading into core modules. A [[private:99_annexes:annex-b-terms-and-definitions:p:provider_contract|Provider Contract]] formalizes the obligations of the abstraction, while a [[private:99_annexes:annex-b-terms-and-definitions:p:provider_plugin|Provider Plugin]] realizes those obligations for a particular Provider.+Within the Crucible architecture, the Provider Abstraction supports cloud agnosticism by preventing provider-specific logic from spreading into core modules. A [[public:99_annexes:annex-b-terms-and-definitions:p:provider_contract|Provider Contract]] formalizes the obligations of the abstraction, while a [[public:99_annexes:annex-b-terms-and-definitions:p:provider_plugin|Provider Plugin]] realizes those obligations for a particular Provider.
  
 ===== Definition ===== ===== Definition =====
  
-//provider-independent representation of the capabilities, operations, inputs, outputs, errors, and lifecycle behaviors required from one or more [[private:99_annexes:annex-b-terms-and-definitions:p:provider|providers]]//+//provider-independent representation of the capabilities, operations, inputs, outputs, errors, and lifecycle behaviors required from one or more [[public:99_annexes:annex-b-terms-and-definitions:p:provider|providers]]//
  
 ===== Source ===== ===== Source =====
  • public/99_annexes/annex-b-terms-and-definitions/p/provider_abstraction.1789260163.txt.gz
  • Last modified: 2026/09/12 17:42
  • by nick_dido