Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:p:platform_service [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:p:platform_service [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Platform Service ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Platform Service is a service that supplies a shared technical capability to applications, | ||
| + | |||
| + | A Platform Service may supply: | ||
| + | |||
| + | * Identity | ||
| + | * Authentication | ||
| + | * Authorization | ||
| + | * Name resolution | ||
| + | * Service discovery | ||
| + | * Secret management | ||
| + | * Key management | ||
| + | * Configuration distribution | ||
| + | * Logging | ||
| + | * Monitoring | ||
| + | * Messaging | ||
| + | * Data storage | ||
| + | * Repository access | ||
| + | * Policy enforcement | ||
| + | * Network management | ||
| + | |||
| + | A Platform Service may operate: | ||
| + | |||
| + | * As a [[public: | ||
| + | * On a [[public: | ||
| + | * Through a [[public: | ||
| + | * As part of a [[public: | ||
| + | * Within another platform realization | ||
| + | |||
| + | A Platform Service differs from an application service: | ||
| + | |||
| + | * A Platform Service supplies a shared technical capability used by other subjects | ||
| + | * An application service performs a domain or business function | ||
| + | |||
| + | The distinction depends on the architectural role assigned to the service. | ||
| + | |||
| + | A Platform Service differs from an [[public: | ||
| + | |||
| + | * An Infrastructure Resource supplies an infrastructure capability | ||
| + | * A Platform Service exposes a shared service capability through an operational interface | ||
| + | |||
| + | A Platform Service may depend on one or more Infrastructure Resources. | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //service that supplies a shared technical capability to applications, | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Platform Service does not by itself establish that the service is: | ||
| + | |||
| + | * Available | ||
| + | * Securely configured | ||
| + | * Compliant | ||
| + | * Authorized for use | ||
| + | * Suitable for production operation | ||
| + | * Accessible from every environment | ||
| + | |||
| + | Separate requirements govern those characteristics. | ||
| + | |||
| + | The term does not prescribe a deployment model, implementation technology, provider, interface protocol, or hosting platform. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | An identity service deployed within an Infrastructure Environment supplies authentication and authorization capabilities to multiple Containerized Workloads and platform components. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||