Recipe-Based Service Coordination for Automated Authorization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In large and complex service-oriented systems, the manual testing and approval processes for new or changed operations often lead to bottlenecks, delaying the addition of new features and requiring complex manual coordination among services.
Innovation Solution
A service coordination system that uses recipes, where a recipe builder compiles service operations into directed acyclic graphs, allowing for automated generation and execution of service operations, enabling rapid and efficient addition of new features without manual approval, and supporting changes to recipes with automatic recompilation and updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual testing and approval processes are used for new operations, then system reliability is maintained through human review, but productivity decreases due to bottlenecks and delays
Solution Approach 1:
The system performs self-verification through automated testing frameworks and validation rules embedded in the recipe compilation process. The service coordination system automatically detects and prevents errors through programmatic checks, eliminating the need for manual review while maintaining system reliability.
Solution Approach 2:
Manual testing and approval processes are replaced with automated computational systems. The patent implements automated service operation testing, validation, and coordination through software-based mechanisms that systematically verify operations without human intervention, thereby maintaining reliability while dramatically improving productivity.
2Reliability
If manual coordination among services is used, then complex service interactions are carefully managed, but device complexity increases due to coordination overhead
Solution Approach 1:
The patent introduces a service coordination system as an intermediary layer between services. This mediator automatically manages service interactions, handles dependencies, and coordinates operations through standardized interfaces. The coordination complexity is encapsulated within the mediator rather than being distributed across individual service coordinators, reducing overall system complexity while maintaining accurate service coordination.
Solution Approach 2:
The coordination system is divided into modular components including recipe builders, service operation definitions, and automated testing frameworks. Each service operation is independently defined and tested, allowing complex coordination tasks to be broken down into manageable, reusable units that reduce overall coordination complexity.
3Productivity
If automated recipe-based coordination is implemented, then productivity increases through rapid feature addition, but ease of operation decreases due to automated process complexity
Solution Approach 1:
The system uses templates and reusable recipe patterns that can be copied and adapted for new service operations. Instead of creating coordination logic from scratch for each feature, developers can replicate proven patterns, significantly reducing the operational complexity while maintaining high productivity. The recipe builder automatically generates standardized coordination logic based on these templates.
4Stability of the object's composition
If manual approval processes are used for service changes, then system stability is maintained through human review, but loss of time increases due to approval delays
Solution Approach 1:
The system performs preliminary automated validation and testing during the recipe compilation phase, before deployment. Service operations are pre-verified against defined rules and constraints, and potential issues are detected early in the development process. This preliminary action ensures system stability is maintained while eliminating time-consuming manual approval delays.
Data Source
AI summary
Methods, systems, and computer-readable media for request authorization using service coordination are disclosed. An authorization data structure and an operation data structure are selected based at least in part on a request for an operation. The authorization data structure comprises a directed acyclic graph representing a flow of data between service operations associated with authorization of the operation, and the operation data structure comprises a directed acyclic graph representing a flow of data between a service operations associated with execution of the operation. Authorization of the operation is attempted using the authorization data structure, comprising invoking one or more of the service operations associated with authorization. If the authorization is successful, then the execution of the operation is initiated using the operation data structure, comprising invoking one or more of the service operations associated with execution.