Behavior Tree Microservice Orchestration for Flexible Service Chains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current microservice orchestration methods are cumbersome and complex, making it difficult to modify or introduce new services into a service chain, especially when requiring changes in the development and deployment processes.
Innovation Solution
A microservice orchestration method that establishes nodes in a runtime to control microservice execution, receives user construction on a behavior tree, parses the tree to map nodes to microservices, and generates an instance of the behavior tree, allowing for flexible orchestration of microservices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If microservices are orchestrated in a fixed order using traditional workflow methods, then the system maintains stability and predictability, but the complexity of development and deployment increases significantly when services need to be modified or introduced
Solution Approach 1:
The patent segments the service chain into independent service nodes that can be individually configured and managed. Each service is represented as a discrete node in the behavior tree, allowing independent modification without affecting the entire system. This segmentation enables flexible addition or modification of services while maintaining overall system stability.
Solution Approach 2:
The patent implements dynamic orchestration where the service chain configuration can be modified at runtime through behavior tree construction. The system transitions from static fixed-order orchestration to dynamic configurable orchestration, allowing services to be added, removed, or reconfigured without redeploying the entire system.
2Ease of manufacture
If traditional fixed-order orchestration is used, then the implementation is straightforward, but any modification requires cumbersome and complex development and deployment processes
Solution Approach 1:
The patent establishes service nodes and behavior tree structures in advance, defining the orchestration framework before specific services need to be deployed or modified. This preliminary setup creates a reusable template that accelerates future service additions and modifications, eliminating the need for complex development processes each time a service changes.
Solution Approach 2:
The patent uses behavior tree templates that can be copied and reused for different service configurations. Once a behavior tree is constructed for a particular service chain, it can be replicated and adapted for new services, significantly reducing development time and effort for service modifications.
3Adaptability or versatility
If services are tightly coupled in a fixed orchestration chain, then the system structure is simple, but the coupling between microservices becomes excessive and hinders flexibility
Solution Approach 1:
The patent introduces behavior trees as an intermediary layer between individual microservices and the orchestration logic. This mediator decouples services from each other, allowing them to remain independent while still enabling coordinated execution through the behavior tree structure. Services communicate through standardized interfaces defined by the behavior tree nodes.
Solution Approach 2:
The behavior tree structure serves multiple functions simultaneously: it defines service execution order, manages service dependencies, enables dynamic configuration, and provides a standardized interface for service integration. This universal structure handles various orchestration requirements without requiring tight coupling between services.
Data Source
AI summary
Embodiments of this application mainly relate to the field of data processing technologies, and in particular, to microservice orchestration methods and apparatus, electronic devices, and readable media. A first node is established in a first runtime for each of a plurality of microservices. The first node is configured to control execution of the microservice. Construction performed by a user on a behavior tree is received. The behavior tree includes a leaf node, and the leaf node represents the microservice. The behavior tree is parsed, where the leaf node is mapped to the first node. An instance of the behavior tree is generated.