Overview#
Service definition varies depending on whom you ask and within a provided contextLDAPWiki refers you to service
Service - is a mechanism to access an underlying capability.” (OASIS)!! Service within Microservices
Service generally, has an API, which provides its clients with access to its functionality. The implementation of its functionality is hidden.!! Service Domain-Driven Design
A Service in Domain-Driven Design, when an operation does not conceptually belong to any object.
Following the natural contours of the problem, you can implement these operations in services.
The term Service refers to a software functionality or a set of software functionalities (such as the retrieval of specified information or the execution of a set of operations) that can be reused by different clients for different purposes, together with the policies that should control its usage (based on the identity of the client requesting the Service, for example).
OASIS defines service as "a mechanism to enable access to one or more capabilities, where the access is provided using a prescribed interface and is exercised consistent with constraints and policies as specified by the service description.
Service-oriented Architecture Service#
Service-oriented Architecture a Service has four properties according to one of many definitions:[1]- Service logically represents a business activity with a specified outcome.
- Service is self-contained.
- Service is a black box for its Consumer of services
- Service may consist of other underlying Services.[3]
Services#
More Information#
There might be more information for this subject on one of the following:- AWS CloudFormation
- AWS Elastic Container Service
- AWS Simple Queue Service
- Access Control Engine
- Adoption
- Advertisement
- Apple ID
- Attack Orchestrator
- Attack Service
- Bounded Context
- Certificate Transparency
- Cloud
- Cloud Native
- Cloud Pricing
- Cloud computing
- Commodity
- Computing platform
- Connection Draining
- Consumer of services
- Credential Service Provider
- Creditor
- Cyber Attack as a Service
- DNS Privacy Considerations
- Data Ownership
- Deming
- Digital Identity
- Digital Identity Acceptance Policy
- Domain Name System
- DynamoDB
- Electronic Health
- Exchange
- FALLOUT
- FIDO Alliance Metadata Service
- Facebook Messenger
- Facial Analysis, Comparison, and Evaluation
- Faythe
- GCP Project Owner
- GCP Resource
- Gmail
- Google API Explorer
- Google Cloud Platform
- Google Key Management Service
- Help Desk
- IMessage
- Identity Broker
- Identity Proofing
- Independent contractor
- Java Cryptography Extensions
- Key Management
- Key Management Service
- Kubernetes
- Kubernetes Service
- Link Relation Types
- Market
- Medium of exchange
- Mellanox Technologies
- Microservice
- Middleware
- Modular Open Source Identity Platform
- Money
- Monopoly
- Monopsony
- Password Reuse
- Payment
- Phantom Token Flow
- Policy Based Management System
- Product
- Proxy Server
- Public Data Network
- Quality of Service
- Resource Inventory Service
- Service-oriented Architecture
- ServiceOutput
- Session Affinity
- Shared Responsibility Model
- Sovrin
- TRUSTED_FOR_DELEGATION
- The Next Big Thing
- Time synchronization
- Trusted Service Manager
- United Nations Standard Products and Services Code
- Verify Time is Synchronized
- Virtual Private Cloud
- Why is Time Important
- [#1] - Service-oriented_architecture - based on information obtained 2016-12-22-