Microservice Load Balancing for Virtual Distributed Ledger Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain systems lack flexibility to adapt to specific use-cases and do not support dynamically configurable platforms that can create and interact with different types of distributed ledger technology (DLT) networks, limiting their ability to compose specific DLT needs and interoperate across various networks.
Innovation Solution
The implementation of virtual distributed ledger networks (vDLN) using microservices-based architecture, allowing vDLT nodes to participate in multiple DLT/blockchain networks, leverage compute, storage, and network resources, and interoperate across permissioned private and public networks, with features like event routing, smart contract execution, and transaction management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a specific type of blockchain technology is used, then the system can provide stable and reliable performance, but it cannot adapt to different use-cases or support multiple DLT networks
Solution Approach 1:
The patent implements a universal DLT platform that can host multiple types of distributed ledger technology networks (permissioned, public, hybrid) within a single system. The platform provides common infrastructure services that work across different DLT types, allowing one system to perform multiple functions and support various use-cases without requiring separate specialized systems for each blockchain type.
Solution Approach 2:
The system segments DLT functionality into independent modules including separate microservices for different DLT network types, isolated container environments for each blockchain instance, and modular consensus mechanisms. This segmentation allows the platform to support multiple DLT networks simultaneously while maintaining stability and preventing interference between different blockchain types.
2Adaptability or versatility
If multiple DLT networks are supported, then interoperability and versatility are improved, but system complexity and resource management difficulty increase
Solution Approach 1:
The patent introduces intermediary components including a unified API layer that mediates between clients and multiple DLT networks, a resource orchestration service that manages allocation across networks, and standardized translation layers that handle protocol conversions. These intermediaries simplify resource management and allow the system to support multiple DLT networks without proportionally increasing complexity.
Solution Approach 2:
The system dynamically adjusts operational parameters such as resource allocation, consensus thresholds, and network configuration based on the specific DLT network being accessed. This parameterization allows the same underlying infrastructure to efficiently support different blockchain types by changing configuration parameters rather than requiring separate hard-coded systems for each network type.
3Adaptability or versatility
If microservices architecture is implemented, then flexibility and adaptability are improved, but system complexity and operational difficulty increase
Solution Approach 1:
The patent merges the management of multiple independent microservices into unified orchestration layers and aggregate service interfaces. While individual microservices remain independent for flexibility, their collective management is consolidated through centralized service meshes, unified configuration management, and aggregated monitoring systems, reducing operational complexity despite the underlying microservices architecture.
Data Source
AI summary
The present disclosure relates to systems and methods for microservice execution load balancing in virtual distributed ledger networks. In one embodiment, a system comprises a plurality of hardware processors; and at least one memory device storing processor-executable instructions to perform operations comprising: creating one or more virtual machines or containers; and executing a plurality of microservices via the one or more virtual machines or containers, wherein the plurality of microservices includes: a smart contract execution microservice configured to execute a smart contract after receiving a smart contract microservice request; and a load balancer microservice configured to distribute hardware processing load associated with the smart contract execution microservice across the plurality of hardware processors.