Dynamic Mesh Service Generation for Microservice Data Aggregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The Backend for Frontend (BFF) layer in microservices architecture faces challenges such as high effort in incorporating new requirements, potential bottlenecks, and single-point failures when combining data from multiple services, as well as difficulties in applying features like resilience.
Innovation Solution
The system generates a mesh service dynamically by using a Mesh-Operator-SVC that receives input defining the new mesh service, validates it, and triggers its creation. This mesh service is designed to fetch data from multiple service containers, parsing inputs and generating REST APIs while applying resilience configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a BFF layer is implemented to combine data from multiple small services, then data aggregation capability is improved, but system complexity and effort to incorporate new requirements increase
Solution Approach 1:
The patent segments the data aggregation function by introducing dynamic mesh services that can be independently created and configured for different service combinations. Each mesh service handles specific data aggregation requirements, allowing the system to scale and adapt without increasing overall BFF layer complexity.
Solution Approach 2:
The patent implements dynamic mesh services that can be created, modified, and destroyed on-demand based on specific data aggregation requirements. This dynamic approach allows the system to adapt to new requirements without permanently increasing system complexity, as mesh services are created only when needed.
2Adaptability or versatility
If the BFF layer combines data from many services, then data aggregation capability is improved, but the BFF layer becomes a bottleneck and single-point failure
Solution Approach 1:
The patent distributes the data aggregation function across multiple dynamic mesh services instead of concentrating it in a single BFF layer. Each mesh service handles specific service combinations, eliminating the single-point failure risk while maintaining data aggregation capability.
Solution Approach 2:
The patent introduces dynamic mesh services as intermediary components between the BFF layer and multiple small services. These mesh services act as distributed mediators that handle data aggregation, preventing the BFF layer from becoming a bottleneck or single-point failure.
3Adaptability or versatility
If the BFF layer is responsible for combining many services, then data aggregation capability is improved, but ease of applying features like resilience decreases
Solution Approach 1:
The patent segments the data aggregation function into independent mesh services, each with its own feature configuration. This allows features like resilience to be applied independently to each mesh service through configuration files, making it easier to implement and manage features without affecting the entire BFF layer.
Solution Approach 2:
The patent enables dynamic creation and configuration of mesh services with specific feature sets. Features like resilience can be dynamically applied to individual mesh services based on their specific requirements, making it easier to implement features without modifying the entire BFF layer architecture.
Data Source
AI summary
Disclosed herein are system, method, and computer program product embodiments for a dynamic generation of a mesh service. An embodiment operates by receiving, by at least one processor, an input indicating a plurality of service containers, and retrieving a container image from a container repository responsive to the receiving of the input. The embodiment further operates by creating a new container image based on the container image and the plurality of service containers indicated in the input. In addition the embodiment operates by creating a component by calling an application programming interface (API) of an orchestration platform, and receiving, from the remote server, the additional user attribute data. Then the embodiment operates by creating the mesh service based on the new container image and the component.