Event-Based Distributed Order Orchestration Decoupling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing order management systems face challenges in accurately modeling business processes due to skill set differences between business architects and IT designers, leading to implementation discrepancies and inefficiencies, particularly in long-running processes and tight coupling of systems in web service environments.
Innovation Solution
A distributed order orchestration system that includes a capture layer, decomposition layer, orchestration layer, task layer services, external interface layer, and global order promising layer, utilizing an event manager to process orders by determining steps based on process state and metadata, and publishing events across an event messaging system for task execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If traditional BPEL orchestration language is used to model business processes, then business processes can be automated, but implementation discrepancies occur due to skill set differences between business architects and IT designers
Solution Approach 1:
The patent introduces an event-driven intermediary layer that sits between business process definition and system execution. Events serve as standardized intermediaries that translate business intent into system actions, eliminating the need for IT designers to directly code complex orchestration logic and reducing implementation discrepancies.
Solution Approach 2:
The patent segments the business process into discrete, independent events rather than continuous orchestration flows. Each event represents a specific business occurrence that can be independently defined, managed, and executed, making the process model more precise and easier to align with actual business operations.
2Reliability
If long-running business processes are used to store all associated data, then complete process information is maintained, but system throughput becomes bottlenecked
Solution Approach 1:
The patent extracts process state management from long-running process instances by using persistent event logs. Instead of maintaining all process data in memory within active process objects, the system extracts and stores process state information in external event logs, allowing processes to complete quickly while preserving complete process information for later retrieval and analysis.
3Adaptability or versatility
If web service environment with tight coupling is used to integrate different systems, then system integration is achieved, but system flexibility and maintainability are reduced
Solution Approach 1:
The patent introduces events as intermediary objects that mediate between different systems and processes. Instead of direct point-to-point integrations between systems, all interactions are published as events that can be consumed by multiple subscribers, decoupling systems while maintaining integration capabilities and improving flexibility.
Data Source
AI summary
A distributed order orchestration system is provided that includes an event manager configured to generate and publish a set of events based on a process state and metadata stored in a database. A set of subscribers can consume the set of events, and each subscriber can execute a task based on the consumed event.