Dynamic Workflow Builder with Blue-Green Server Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current workflow management systems are costly and require specialized knowledge to define and manage workflows, and they face challenges in handling server-level switchover in blue-green topologies, leading to potential downtime and complications when not all software is production-ready.
Innovation Solution
A system with a gateway router that routes requests to server clusters based on credentials, allowing finer control over software versions and enabling users to define workflows without extensive knowledge, using a blue-green topology with additional designations like 'yellow' and 'purple' for more nuanced stability and error tolerance, and a form-based, drag-and-drop interface for creating workflows.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a blue-green topology is used for server switchover, then system stability is improved, but complexity of managing multiple software versions increases
Solution Approach 1:
The patent segments the server cluster into distinct blue (production) and green (development) environments, allowing independent management of each. This segmentation enables simultaneous operation of stable production systems and experimental development systems without interference, resolving the contradiction by organizing complexity into isolated, manageable portions while maintaining overall system stability.
Solution Approach 2:
The patent introduces a router as an intermediary component that manages traffic routing between clients and server clusters. The router mediates the complexity of version management by automatically directing requests to appropriate software versions based on configuration, abstracting the complexity from users while maintaining stable system operation through controlled switchover mechanisms.
2Reliability
If specialized software development knowledge is required to define workflows, then workflow management capability is improved, but accessibility to non-technical users deteriorates
Solution Approach 1:
The patent implements self-service through automated workflow initiation based on document receipt. The system automatically extracts data from uploaded documents, identifies required workflows, and initiates appropriate workflows without requiring user intervention or technical knowledge. This transforms the system from requiring specialized expertise to serving itself, enabling non-technical users to access sophisticated workflow management capabilities simply by uploading documents.
Solution Approach 2:
The patent replaces manual, technical configuration processes with automated mechanical systems. Instead of requiring users to manually configure workflows through complex interfaces, the system uses automated document processing, data extraction, and workflow triggering mechanisms. This substitution of manual technical operations with automated systems eliminates the barrier to entry for non-technical users while preserving full workflow management functionality.
3Reliability
If all software must be production-ready before switchover, then system reliability is improved, but productivity of deploying new features deteriorates
Solution Approach 1:
The patent segments the software deployment process into independent blue and green environments, allowing different levels of readiness across different software components. Production-critical software can remain in the blue environment while experimental features are developed in the green environment. This segmentation enables selective switchover of individual components without requiring all software to be production-ready, thereby improving both reliability and productivity.
Solution Approach 2:
The patent applies partial action by enabling switchover of individual software components or features rather than requiring complete system readiness. The system allows selective promotion of specific workflows or functions from development to production based on their individual readiness status. This partial switchover approach enables deployment of new features without compromising overall system reliability, as only the specific component being deployed undergoes the switchover while other components remain in their original state.
4Manufacturing precision
If detailed control over workflow versioning is implemented, then workflow management precision is improved, but ease of operation deteriorates
Solution Approach 1:
The patent implements self-service automation in workflow versioning, where the system automatically manages version creation, tracking, and switchover based on predefined criteria. Instead of requiring users to manually control versioning details, the system autonomously handles versioning precision through automated document processing, data extraction, and workflow initiation. This automation maintains precise version control while eliminating the operational complexity from user interactions.
Solution Approach 2:
The patent introduces automated intermediaries that handle the complexity of versioning between user actions and system state changes. These intermediaries include automated document processors, data extractors, and workflow trigger mechanisms that translate simple user inputs into precise version-controlled actions. The intermediaries absorb the complexity of versioning precision while presenting a simple, easy-to-use interface to users, thereby resolving the contradiction between precision and ease of operation.
Data Source
AI summary
Systems and methods for routing requests to a plurality of server clusters are disclosed, especially in a workflow management context. A first server cluster handles requests concerning a first software version and a second server cluster responds to requests concerning a second version of that same software. Upon receiving a request to change default routing of requests, a configuration of a gateway router is updated and subsequent requests concerning the first software are routed to the second server cluster while subsequent request concerning the second software remain routed to the first server cluster. A first graphical user interface (GUI) is provided to be used in defining a series of steps in a workflow and to creating a secondary GUI that will be used when performing the series of steps. Tools for automation and data extraction during the workflow are provided and workflow state is tracked until completion of the workflow.