Metadata Driven Orchestration Engine Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing code-based approach for implementing and maintaining middle-tier systems in computer networks, such as order management systems for financial products, is time-consuming and difficult due to the need for extensive coding and orchestration of business logic and data retrieval services.
Innovation Solution
A configuration file-based approach that specifies orchestration steps and activities, allowing for the generation of metadata code artifacts which are used by an orchestration engine to manage calls to back-end systems, eliminating the need for explicit coding and enabling stateless orchestration of system activities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a code-based approach is used to implement middle-tier systems, then the system can perform business logic execution and data retrieval services, but the implementation, testing and maintenance effort increases significantly
Solution Approach 1:
The patent extracts business logic and orchestration rules from traditional code implementations and places them into configuration files. This separation allows the system to maintain full functionality while eliminating the need for extensive coding, thereby reducing implementation, testing, and maintenance effort without sacrificing system reliability
Solution Approach 2:
The patent replaces the mechanical process of coding business logic with an automated configuration-based system. The orchestration engine automatically interprets configuration files and generates the necessary execution logic, substituting manual programming activities with automated system processes that reduce human effort and error
2Productivity
If code is written for business logic and orchestration, then the system can execute activities, but the time required to implement and test the system increases
Solution Approach 1:
The patent implements preliminary action by pre-defining business logic and orchestration rules in configuration files before system execution. The orchestration engine pre-compiles and validates these configurations, so that during runtime, the system can execute activities immediately without requiring additional coding or testing time
Solution Approach 2:
The patent uses configuration files as templates that can be copied and reused across different implementations. Once business logic is defined in a configuration file, it can be replicated and adapted for multiple use cases without rewriting code, significantly reducing implementation time while maintaining execution capability
3Ease of operation
If traditional orchestration approaches are used, then system activities can be coordinated, but the skill requirements and complexity increase
Solution Approach 1:
The patent introduces an orchestration engine as an intermediary layer between configuration files and system activities. This engine handles the complexity of coordinating multiple services and activities automatically, allowing users to define simple configuration rules without needing to understand the underlying orchestration complexity, thereby reducing skill requirements while maintaining orchestration capability
Data Source
AI summary
An efficient reusable, extensible light weight framework statelessly orchestrates system activities in any application which involves a series of sequential or parallel set of activities involving computational logic, data retrieval and persistence services. Actual orchestration steps and activities and computational logic are specified into configuration files, separate from the orchestration engine itself, thereby eliminating the need to code for such logic and activities. The framework can eliminate the need to code business logic and orchestration of data retrieval services by externalizing them into configuration files, resulting in lower costs to implement, test and maintain such system during its lifespan.