Graph Knowledge Base for Stateful Cloud-Native Apps
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software development practices are inadequate for building flexible and responsive stateful cloud-native applications, as they rely on static, linear processes and rigid middleware stacks, which limit the ability to leverage contextually relevant resources and lead to suboptimal outputs due to inefficient coordination and communication between tasks and systems.
Innovation Solution
A computing system platform that uses a graph knowledge base for declarative modeling and processing, enabling the creation of contextually-motivated network service instances through normalized lifecycle management operations, which are bound to micro-capabilities and managed for execution, storage, and network allocation, facilitating dynamic and scalable application behavior.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If static, linear processes and rigid middleware stacks are used, then implementation simplicity is maintained, but flexibility and responsiveness to external events deteriorate
Solution Approach 1:
The patent implements dynamic processes that can adapt to external events in real-time. The system transitions from static, pre-defined workflows to dynamic workflows that can be modified at runtime based on contextual events, enabling the system to respond flexibly to changing conditions while maintaining manageable complexity through structured event handling mechanisms.
Solution Approach 2:
The system allows parameters of processes and workflows to be changed dynamically based on external events. Configuration parameters, routing decisions, and process behaviors can be adjusted at runtime without requiring complete process redefinition, enabling adaptability while maintaining a structured framework that prevents complexity from becoming unmanageable.
2Productivity
If tasks and systems work in isolation, then coordination overhead is reduced, but output quality and resource sharing efficiency deteriorate
Solution Approach 1:
The patent introduces event streams and message brokers as intermediary components that facilitate communication and coordination between isolated tasks and systems. These intermediaries enable efficient resource sharing and information exchange without requiring direct point-to-point connections, thereby improving output quality through better coordination while managing complexity through standardized communication protocols.
Solution Approach 2:
The system segments coordination functions into modular event handlers and message processing components. Each task or system can maintain isolation while participating in coordinated workflows through well-defined event interfaces, allowing high-quality output through effective collaboration without overwhelming coordination complexity.
3Adaptability or versatility
If pre-defined parameterization is used, then process stability is maintained, but contextually relevant resource exploitation is limited
Solution Approach 1:
The patent implements dynamic parameterization where process parameters can be adjusted based on contextual events while maintaining a stable core workflow structure. The system distinguishes between stable process frameworks and dynamic parameter values, allowing contextual resource exploitation through event-driven parameter adjustments without compromising overall process stability.
Solution Approach 2:
The system applies local quality changes by allowing specific parameters to be customized based on contextual events while maintaining global process stability. Different parts of the process can have different levels of adaptability, with critical path elements maintaining stability while peripheral elements can exploit contextual resources dynamically.
Data Source
AI summary
Receive an order, the order indicating a network service model. Identify a context of the order based on metadata. Generate, using the network service model, a deployment plan, the deployment plan facilitating an instantiation of a contextually-motivated network service instance as a set of normalized lifecycle management (LCM) operations performed against at least one of a plurality of associated service entities. Deploy the deployment plan, wherein to deploy the deployment plan causes the system to bind each of the normalized LCM operations, based on the context of the order, to one or more respective micro-capabilities, each of the respective micro-capabilities having previously been onboarded to the system as one or more corresponding modeled objects capable of being declaratively composed, each of the corresponding modeled objects including a mapping of standard LCM operations to one or more existing micro-capabilities of the system, and manage execution of the one or more respective micro-capabilities and associated resources, associated storage, and associated network and service allocation and configuration, to instantiate the contextually-motivated network service instance, wherein to manage the execution of the one or more micro-capabilities causes the system to fulfill the order as a transaction providing guarantees, and applying any of compensations and rollback automatically. Trace the transaction based on the metadata, thereby simplifying test and debug operations and run-time observability.