Service-Oriented API Migration via Context-Aware Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing service-oriented architectures face inefficiencies due to multiple round trip network interactions and unresolved dependencies when migrating from procedural or object-oriented APIs, which are not optimized for self-contained service requests.
Innovation Solution
Migrating non-service-oriented APIs to a service-oriented architecture by identifying primary and secondary concerns, grouping them into self-contained services, and using service context data such as profiles, request parameters, and filters to address secondary concerns within a service-oriented context.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If procedural or object-oriented APIs are used with rich client applications, then functionality can be provided with tightly defined interfaces, but multiple round trip network interactions are required to accomplish single tasks
Solution Approach 1:
The patent segments the API into self-contained services with well-defined interfaces. Each service is designed to encapsulate specific business logic and data, allowing independent invocation without requiring multiple round trips. This segmentation enables the system to maintain clear interface definitions while reducing network interaction overhead by composing services to accomplish tasks in fewer calls.
Solution Approach 2:
The patent implements a universal service framework that can handle multiple types of operations through a common service-oriented interface. The service framework provides multi-functional capabilities, allowing a single service call to perform multiple related operations or to serve different client needs, thereby reducing the total number of network interactions required.
2Ease of manufacture
If procedural or object-oriented APIs are used, then tightly defined interfaces can be established, but unresolved dependencies cause delays
Solution Approach 1:
The patent applies preliminary action by pre-resolving dependencies at service definition time. The service framework analyzes service dependencies and resolves them before runtime execution, ensuring that all required services and resources are ready in advance. This eliminates runtime dependency resolution delays and allows services to be invoked immediately without waiting for unresolved dependencies.
Solution Approach 2:
The patent introduces a service framework as an intermediary layer between clients and underlying services. This framework acts as a mediator that handles dependency resolution, service composition, and coordination automatically. The intermediary absorbs the complexity of dependency management, shielding clients from unresolved dependencies and eliminating associated delays.
3Productivity
If service-oriented architecture is implemented, then self-contained services can be provided, but migration from existing APIs requires identifying and grouping primary and secondary concerns
Solution Approach 1:
The patent segments the migration process into systematic steps: identifying primary concerns (core business operations), identifying secondary concerns (contextual information), grouping related concerns into services, and defining service interfaces. This segmentation transforms the complex migration task into manageable phases, making the process more structured and less daunting while maintaining high service request efficiency.
Solution Approach 2:
The patent applies parameter changes by transforming the API design parameters from procedural/object-oriented to service-oriented paradigms. This involves changing how services are defined, how interfaces are structured, and how dependencies are managed. By systematically adjusting these parameters during migration, the patent achieves self-contained services without overwhelming complexity in the migration process.
Data Source
AI summary
Migrating a computer-provided solution to a service-oriented architecture is disclosed. One or more primary concerns, each representing a core operation of the computer-provided solution, are identified. One or more secondary concerns, each being associated with a manner in which a core operation of the computer-provided solution is performed, are identified. One or more services, each of which addresses one or more of said one or more primary concerns in a manner determined at least in part by a service context configured to address one or more of said one or more secondary concerns at least in part by indicating as applicable a manner in which applicable ones of said one or more services are to be performed, are defined.