Service Integration Connector
(Redirected from Service Adapter)
Jump to navigation
Jump to search
A Service Integration Connector is a service-oriented API-driven integration connector that can support service integration tasks between service providers and service consumers.
- AKA: Service Adapter, Service Bridge, Service Integration Adapter.
- Context:
- It can typically expose Service Interfaces through service endpoints providing service operations, service contracts, and service metadata.
- It can typically implement Service Protocols through protocol handlers supporting service invocation, service discovery, and service binding.
- It can typically manage Service Lifecycles through lifecycle managers handling service initialization, service activation, and service deactivation.
- It can typically enforce Service Level Agreements through SLA monitors tracking service availability, service performance, and service reliability.
- It can typically handle Service Versionings through version managers supporting version negotiation, version routing, and version compatibility.
- ...
- It can often provide Service Compositions through orchestration engines enabling service chaining, service aggregation, and service workflow.
- It can often enable Service Mediations through mediation layers performing message transformation, protocol bridging, and content enrichment.
- It can often support Service Securitys through security frameworks implementing service authentication, service authorization, and service encryption.
- It can often maintain Service Registry Integrations through registry clients facilitating service registration, service lookup, and service metadata management.
- ...
- It can range from being a Basic Service Integration Connector to being an Advanced Service Integration Connector, depending on its service integration capability.
- It can range from being a REST Service Integration Connector to being a SOAP Service Integration Connector, depending on its service protocol support.
- It can range from being a Loosely-Coupled Service Integration Connector to being a Tightly-Coupled Service Integration Connector, depending on its service coupling degree.
- It can range from being a Single-Service Integration Connector to being a Multi-Service Integration Connector, depending on its service integration scope.
- It can range from being a Cloud Service Integration Connector to being an On-Premise Service Integration Connector, depending on its service deployment model.
- ...
- It can integrate with Enterprise Service Bus for service orchestration.
- It can connect to API Management Platform for service governance.
- It can interface with Service Mesh for service communication.
- It can communicate with Identity Provider for service authentication.
- It can synchronize with Service Catalog for service documentation.
- ...
- Example(s):
- Web Service Integration Connectors, such as:
- RESTful Service Integration Connectors, such as:
- SOAP Service Integration Connectors, such as:
- Cloud Service Integration Connectors, such as:
- AWS Service Integration Connectors, such as:
- Azure Service Integration Connectors, such as:
- Agent Service Integration Connectors, such as:
- ...
- Web Service Integration Connectors, such as:
- Counter-Example(s):
- File-Based Integration, which uses file transfer rather than service invocation.
- Database Link, which uses direct database connection rather than service interface.
- Batch Processing System, which lacks real-time service interaction.
- See: Integration Connector, Service Integration, Web Service, API Integration, Service-Oriented Architecture, Microservice Integration, Enterprise Service Bus.
- Reference(s):