Unified API Platform for Workflow Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current API systems require significant time and resources to create and maintain separate infrastructure for each API or workflow, leading to high maintenance overhead and inefficient use of computing resources, especially when performing multiple actions or workflows.
Innovation Solution
A common platform with a unified API that stores and executes action and workflow information using a shared infrastructure, allowing for the creation and execution of multiple workflows without additional maintenance or resource allocation from the user, and providing uniform monitoring across all workflows.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate infrastructure is created for each API or workflow, then each workflow can be independently designed and executed, but maintenance overhead increases and computing resources are wasted
Solution Approach 1:
The patent implements a universal fulfillment platform that can execute multiple different workflows and actions through a single shared infrastructure. The platform stores action information and workflow information in databases and uses a common code execution environment, allowing one system to serve multiple purposes without requiring separate dedicated infrastructure for each workflow type.
Solution Approach 2:
The patent merges multiple separate API infrastructures into a single unified fulfillment platform. By combining the execution of different workflows and actions into one shared system with common resources (databases, code execution environment, monitoring mechanisms), the patent eliminates redundant infrastructure while maintaining the ability to independently design and execute different workflows.
2Adaptability or versatility
If separate infrastructure is created for each API or workflow, then each workflow can be independently designed and executed, but computing resources are inefficiently used
Solution Approach 1:
The fulfillment platform is designed as a universal system that handles multiple workflow types through shared computing resources. The same code execution environment, database infrastructure, and monitoring systems serve all workflows, eliminating the need for dedicated resources for each workflow and improving overall computing resource utilization efficiency.
Solution Approach 2:
By merging multiple workflow execution paths into a single shared infrastructure, the patent enables computing resources to be pooled and allocated efficiently across all workflows. The shared nature of the platform allows resources to be reused across different actions and workflows, reducing redundant resource allocation and improving energy efficiency.
3Device complexity
If a common platform is used for multiple workflows, then maintenance overhead is reduced and resources are conserved, but uniform monitoring must be implemented across all workflows
Solution Approach 1:
The patent implements a universal monitoring mechanism that operates across all workflows and actions within the fulfillment platform. The monitoring system is integrated into the shared infrastructure and automatically tracks execution status, success/failure outcomes, and performance metrics for all workflows without requiring separate monitoring systems for each workflow type.
Solution Approach 2:
The monitoring system is designed to automatically detect, measure, and report on workflow execution without requiring manual intervention or complex configuration. The platform self-monitors execution status and generates reports about workflow outcomes, success rates, and performance metrics as part of its normal operation, simplifying the monitoring complexity.
Data Source
AI summary
In some implementations, a device may receive action information, for an action from multiple actions, that indicates at least one of code associated with the action or one or more inputs required to complete the action. The device may receive workflow information, for a workflow included in a set of workflows, that indicates one or more actions from the multiple actions and an order in which the one or more actions are to be completed for the workflow. The device may receive, via an application programming interface (API) call, a request to complete the workflow The device may identify the workflow information associated with the workflow in a data structure. The device may perform the workflow based on the workflow information and the one or more inputs by executing code for the one or more actions indicated by the workflow information and in the order indicated by the workflow information.