Switch-Based Mutex Synchronization for Shared Microservice Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud computing environments with disaggregated resources, there is a lack of coherence and consistency in the access and modification of shared objects or data blocks across microservices, leading to inefficiencies and potential data inconsistencies.
Innovation Solution
Implementing switching architectures that manage mutex primitives to control access to objects or data blocks processed by multiple microservices, ensuring data coherence and consistency across distributed memory and storage systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If disaggregated resources are used to pool compute, storage, memory, and networking resources, then resource utilization and flexibility are improved, but data coherence and consistency across distributed systems deteriorate
Solution Approach 1:
The patent introduces a switch as an intermediary device that manages mutex primitives to control access to shared objects across distributed microservices. The switch acts as a mediator that coordinates between compute nodes, storage nodes, and networking fabric to ensure data coherence while allowing resource disaggregation. This resolves the contradiction by providing centralized coordination (improving reliability) without preventing resource pooling (maintaining adaptability).
Solution Approach 2:
The patent segments the system into distinct functional components: compute nodes, storage nodes, networking fabric, and a centralized switch. Each segment operates independently with specific responsibilities, allowing resources to be disaggregated and allocated flexibly while the switch maintains overall data coherence through mutex management. This segmentation enables both high resource utilization and data consistency.
2Reliability
If mutex primitives are implemented to control access to shared objects, then data consistency is improved, but system complexity increases
Solution Approach 1:
The switch serves as an intermediary that centralizes mutex primitive management, isolating the complexity of data consistency control from individual microservices and nodes. Rather than implementing complex locking mechanisms in every node and service, the switch handles all mutex operations, simplifying the overall system architecture while ensuring data consistency.
Solution Approach 2:
The patent implements virtual representations of mutex primitives in the switch that coordinate access to physical shared objects. The switch maintains virtual mutex states and coordinates access requests, allowing multiple microservices to access shared resources consistently without each service needing to implement its own complex locking logic. This virtualization layer simplifies the system while maintaining reliability.
3Reliability
If centralized switch management is used to coordinate microservices, then data integrity is improved, but network latency increases
Solution Approach 1:
The switch performs preliminary actions by pre-establishing mutex states and access permissions before microservices need to access shared objects. By proactively managing mutex primitives and coordinating access in advance, the switch reduces the need for repeated coordination requests during runtime, thereby maintaining data integrity while minimizing latency overhead.
Solution Approach 2:
The switch maintains continuous mutex management operations, keeping track of shared object access states and coordinating microservice requests in real-time. This continuous coordination ensures data integrity is maintained without requiring periodic re-synchronization or batch processing, reducing latency compared to periodic coordination approaches.
Data Source
AI summary
Switching architectures to manage mutex primitives used to control access to objects or data blocks that are being processed by two or more microservices in a data center are provided.