Service Registry Dynamic Endpoint Provisioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In service-oriented architecture (SOA), low-demand services are often uninstalled or have reduced processing priority, leading to delays and quality issues for service requesters, as existing technologies lack efficient methods for managing and provisioning these services without impacting service quality or causing delays.
Innovation Solution
A method and system where a service registry receives service requests, checks for registered endpoints, and if none exist or performance thresholds are not met, it requests new service providers to create and register new endpoints, allowing for dynamic provisioning and management of services, including virtualization using cloud resources, ensuring continuous service availability and quality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If low demand services are uninstalled or have reduced processing priority to optimize resource usage, then service provider resource utilization is improved, but service availability and quality deteriorate causing delays for service requesters
Solution Approach 1:
The patent implements dynamic service provisioning where services are automatically instantiated or activated in response to service requests. The service registry monitors service availability and dynamically provisions services from service providers when needed, rather than maintaining static service installations. This allows the system to adapt resource allocation based on actual demand while maintaining service availability when required.
Solution Approach 2:
The service registry automatically manages service provisioning without manual intervention. When a service request is received and the service is not available, the registry autonomously contacts service providers, retrieves service endpoints, and updates the registry. This self-service mechanism ensures services are available when needed while optimizing resource usage by not permanently installing low-demand services.
2Loss of energy
If services are uninstalled and removed from active services to free up resources, then resource costs are reduced, but service reinstallation and endpoint configuration cause delays
Solution Approach 1:
Service providers pre-configure services with defined endpoints and service documents before being contacted by the registry. When the registry needs a service, it simply retrieves the pre-configured endpoint information from the service provider rather than performing installation and configuration at request time. This preliminary preparation eliminates reinstallation delays while maintaining resource optimization.
Solution Approach 2:
The service registry maintains copies of service endpoint information and service documents from service providers. Instead of reinstalling services or reconfiguring endpoints when services are requested, the registry uses stored endpoint copies to quickly route requests. This copying mechanism reduces time loss while allowing services to be uninstalled from active deployment.
3Productivity
If processing priority is reduced for low demand services to optimize resource allocation, then high demand service performance is improved, but service quality and contract compliance deteriorate
Solution Approach 1:
The system implements dynamic service activation where services are provisioned with appropriate priority levels based on actual demand and service level agreements. The service registry can request services from providers with appropriate quality requirements and monitor whether services meet agreed performance levels. This allows high-demand services to receive priority processing while low-demand services are activated only when needed, maintaining quality compliance through on-demand provisioning rather than static priority assignment.
Data Source
AI summary
A method, operable by a service registry in a service orientated architecture system, for providing a service within the system. A service request is received from a service requester in the system. The status of the service is checked as registered in the service registry. In response to the service not having a registered service endpoint or a property of the service falling below a defined threshold, a request is sent to service providers or subsequent service registries to provide a new service and according to the defined threshold. In response to a service provider providing the new service according to the defined standard, the service registry is updated with the new service and responding to the service requester that the service is available. The embodiments allow both direct interaction between the requester and provider or indirect interaction via a service management layer.